Gentoo Archives: gentoo-dev

From: Mike Auty <ikelos@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [RFC] New RESTRICT=live value for identification of live ebuilds?
Date: Sat, 02 Aug 2008 12:14:13
Message-Id: 48944F98.6090002@gentoo.org
In Reply to: Re: [gentoo-dev] [RFC] New RESTRICT=live value for identification of live ebuilds? by Zac Medico
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Zac Medico wrote:
5 | Honestly I don't care what the existing scheme is.
6
7 Fair enough, I don't maintain the code or have to deal with the
8 complaints. It seems a waste to abandon an existing scheme though.
9
10 Particularly since RESTRICT is an odd name for random boolean flags.
11 Something like OPTIONS would be better, but it that can't be
12 added/changed quickly. Is there an urgent pressing need for this?
13
14 | primaryuri - Fetch from URLs in SRC_URI before GENTOO_MIRRORS.
15
16 | Looking at the above list I say it's fair game to put just about any
17 | boolean flag in RESTRICT.
18
19 To me, almost every item in that list has "not", "disable", "restrict"
20 or some other negative in it, which lets it fit into a restriction.
21 Primaryuri is the only one that looks out of place.
22
23 You did sound up for a name change though, and if nothing else please do
24 change it. Our new users/developers that don't know RESTRICT is seen as
25 a general purpose options flag will not find it intuitive and will
26 definitely wonder what RESTRICT="live" means. Not everybody knows the
27 ebuild format intimately, and allowing people to easily pick up what's
28 going on is important...
29
30 | That requires an EAPI bump, which also means that it can't be used
31 | in ebuilds with EAPI 0 or 1. The RESTRICT solution is simpler and we
32 | can use it right now in any ebuild.
33
34 It is simpler, and as I say if there's an urgent need then go for it,
35 but to me it feels like it's bolting on functionality into any space
36 it'll go. Given that some time was spent changing all the "noblah"
37 flags to "blah" to fit the RESTRICT name, it's a little disappointing to
38 consider shoving extra flags in it now it all makes sense.
39
40 This is a relatively minor point. In the long run, if people don't like
41 it, it'll get QA bugged/ironed out, if they do it'll stay, you just
42 asked for thoughts... 5:)
43
44 Mike 5:)
45 -----BEGIN PGP SIGNATURE-----
46 Version: GnuPG v2.0.9 (GNU/Linux)
47
48 iEYEARECAAYFAkiUT5cACgkQu7rWomwgFXqqdACfadwat4gS8/O4mX1zwcI+0VeU
49 XawAnjbJa2LXHiK1VMN7ZBf9ICNK+dtl
50 =572l
51 -----END PGP SIGNATURE-----

Replies