Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [RFC] New RESTRICT=live value for identification of live ebuilds?
Date: Sun, 03 Aug 2008 02:49:17
Message-Id: 48951CBD.5050602@gentoo.org
In Reply to: Re: [gentoo-dev] [RFC] New RESTRICT=live value for identification of live ebuilds? by Thomas de Grenier de Latour
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Thomas de Grenier de Latour wrote:
5 > On 2008/08/02, Zac Medico <zmedico@g.o> wrote:
6 >
7 >> USE flags are something that can be enable or disabled
8 >
9 > Here, what the flag would enable/disable is belonging of live packages
10 > to the @live-rebuild set. Compared to the RESTRICT solution, user
11 > gains an easy per-package control of this set (sure, the flag would be
12 > turned on in profiles, so that @live-rebuild is complete by default).
13 >
14 >> but the behavior of the src_unpack() method downloading live sources
15 >> is not something that's generally controlled by a USE flag afaik.
16 >
17 > Right, this "live-rebuild" USE flag would not control anything in the
18 > way the ebuild is executed, but only in the way the package is handled
19 > by Portage. It's not primary usage of USE flags, sure, but it's not
20 > completly unusual neither (for instance, take USE flags which are just
21 > there to trigger some convenience PDEPEND).
22 >
23 >
24 > Anyway, to rephrase / summarize my idea:
25 >
26 > - IUSE="live-rebuild" in the ebuild
27 > ==> triggers LIVEVCS.stable repoman check
28 >
29 > - IUSE="live-rebuild" in the ebuild, and package is installed,
30 > and USE flag "live-rebuild" is enabled for this package
31 > ==> makes it belong to the @live-rebuild set
32 >
33
34 It seems like USE would be an unconventional location to store that
35 information and I'm not sure that it really belongs in the ebuild.
36 Shoehorning it into package.use might have some benefits but USE
37 flags are conventionally used to control ebuild behavior rather than
38 package manager behavior. Perhaps some separate user config file
39 would be more appropriate for that purpose.
40
41 Zac
42 -----BEGIN PGP SIGNATURE-----
43 Version: GnuPG v2.0.9 (GNU/Linux)
44
45 iEYEARECAAYFAkiVHLoACgkQ/ejvha5XGaOq4QCeMZOJcHKn2d2LzhIeRmGrLjlu
46 2J8An1C1lpC5VsCPqnwz4kpPBVEFFRDE
47 =M6Pf
48 -----END PGP SIGNATURE-----