Am 24.12.2012 17:09, schrieb Rick "Zero_Chaos" Farina: > On 12/24/2012 09:00 AM, Diego Elio Pettenò wrote: >> On 24/12/2012 14:32, Ulrich Mueller wrote: >>> This doesn't look right to me. /var/spool contains things like printer >>> queues or outgoing mail that are typically deleted after processing. > >> Not sure how /var/cache fits for binpkgs though, tbh. > > "Application cache data. Such data are locally generated as a result of > time-consuming I/O or calculation. The application must be able to > regenerate or restore the data. The cached files can be deleted without > loss of data." > > No sure how it doesn't... > > Binpackages are really essentially cache created by portage through > time-consuming I/O and calculation (compiling) and can easily be > regenerated locally. Plus, you can delete all of this and the system is > still functional.
Not that I am opposed to keep binpackages in /var/cache - but people on this thread have brought up lot's of reasons why for certain aspects not to keep certain data in certain places. This just hit my mind: can binpackages easily be regenerated locally if their ebuilds are not in portage anymore? I mean they can: grab the ebuild, compile it with the ebuild command, there you go, but isn't that also true for the whole portage tree?
