-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 20/12/12 12:52 PM, Vaeth wrote: > > However, I have strong objections against using /var/cache at all: > FHS explicitly states: > > "Such data is locally generated ... The application must be able > to regenerate or restore the data." >
emerge --sync <-- regenerates/restores the portage tree layman -s <-- regenerates/restores overlays emerge -f @world <-- regenerates/restores any distfiles of consequence download-restricted data whose sole location is in a cache dir is a decision made by the user. Note that current portage has a PORTAGE_RO_DISTDIR var which could be used to specify the path to these fetch-restricted downloads rather than the user putting them directly into /var/cache/distfiles/. Maybe it would be pertinent to suggest and/or include a default path for this? > What is really so bad about the current location under /usr as > default? There were some suggestions about this in the initial thread posts. But /usr/portage is certainly OK to remain as-is, we do not *need* to make any changes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlDTU/AACgkQ2ugaI38ACPDmmwD/XIrHlMiDBU7WPUjp9DILJwuq fM/y5zUVZcoD2W7kcuEA/jPV9l1BH8qsw3UQxJKi6zbjBweD0uJU28jxiX2ybdjo =lBlR -----END PGP SIGNATURE-----
