| |||||||||||||
Survey Says! ....Survey Says! ....Posted Jul 13, 2006 6:19 UTC (Thu) by AnswerGuy (guest, #1256)In reply to: The end of the multiarch era? by skvidal Parent article: The end of the multiarch era?
It was the funniest line in the whole article. My came in to see what I was chuckling about and I read the hole lead in and she's laughing now. (Personally I think it's pretty bone headed to default to empty a cache when a process is quitting due to an error. The most common usage scenarios would entail attempting to fix the error and re-run the process, DUH! If I was implementing something like this I'd make the configuration take a list of flags, percentages, and numeric values (all optional). So you could say: Clean-up: on success; 15%: 800M which would mean: "clean up only if the whole process was successfull (the RPMs are all installed now), or the file systems has less then 15% or 800MiB of free space available (in case I had some real need to build ISO images under that fs that I feel are more pressing than the risk to my cache). Other flags might be: obsolete, never, always (obsolete meaning that we clear the cache of any files for which we've already got an updated version). (Some peope might question why I'd have a percentage and a number --- answer is I might want to have a config that I can use across lots of hosts and I may not want to have to do funning template perl -pi -e 's/..../.../;' stuff to fiddle with calculated sizes).
JimD
(Log in to post comments)
|
|||||||||||||