-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/01/14 11:28 AM, Luis Ressel wrote: > On Thu, 02 Jan 2014 11:10:54 -0500 Ian Stakenvicius > <a...@gentoo.org> wrote: > >> ..or we could just do this, using the existing RESTRICT="mirror" >> that's already in ebuilds -- have a DISTDIR and a >> NODISTCACHEDIR, NODISTCACHEDIR defaults to DISTDIR; if >> RESTRICT="mirror" then distfiles are saved to NODISTCACHEDIR, >> otherwise are saved to DISTDIR. > > IMHO, this is the best solution proposed so far. It doesn't need a > new USE flag duplicating information which is already in RESTRICT > (or am I missing some corner cases here?), and it doesn't bother > those who don't care about this issue with new distfiles-*/ dirs, > as with Kent's proposal. > > @Kent: Why do you think another distinction for RESTRICT=fetch is > neccessary? If it really is, it could also be integrated into this > solution, but I don't get the point -- either you're allowed to > redistribute it, or you're not. RESTRICT=fetch just signals > Portage that it won't be *technically* able to download the > distfiles. > > > Luis >
RESTRICT="fetch" requires the user to do their own fetching; since they're doing that, it should be pretty obvious that the distfile is restricted somehow. Of course, they are still able to do whatever they want, but I expect anyone that is keeping DISTDIR and NODISTCACHEDIR as separate targets would know to not place the fetched distfile in their self-distributing directory, or at least know to read the license restrictions already present in the listed LICENSEs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlLFnksACgkQ2ugaI38ACPCI6gEAmBwKJ3+ce0zkrimGeb6oORVv a2WteMNC9VVeZ+Jce4oA/2ys6+VPZ5AGheVrfL9eakupDPGwbxif78qC6PQ2D28k =gqBF -----END PGP SIGNATURE-----
