-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 René 'Necoro' Neumann wrote: | Zac Medico schrieb: |> Well, RESTRICT has long since evolved into a rather generic set of |> boolean flags and it's quite useful as such. I don't see any need |> for artificial limitations on what types of flags go there. | | For you it is just "one variable amongst others" - and you really don't | care about the relation between its name and its content. But perhaps | just for the sake of easier understanding of ebuilds, this relation | should be kept. Otherwise you'll read in future documentation: "The name | is just for historical reasons and does not reflect the content." -- And | this is nearly always a stumbling block for the non-experienced. | | Perhaps in a later EAPI RESTRICT might be renamed to something like | FLAGS - and then can really be used as a pool of flags.
Can the RESTRICT="live" value be interpreted as , 'restrict this ebuild to live repositories' or , if you want, 'this package will only build from live repos'? In either case, I don't see the fuss regarding this naming thing, considering RESTRICT is already being used for similar functionality. Regards, - -- Luis F. Araujo "araujo at gentoo.org" Gentoo Linux -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkiU9e8ACgkQNir3WYj9aLpH0wCfS0t7t9md+kPmVZsppiekybe4 TNUAoIsGXS+wnGTpqZRNLpRTLwSGG7vk =xLIG -----END PGP SIGNATURE-----
