On 13:39 Sat 23 Aug , Zac Medico wrote: > Please consider a PROPERTIES=live value that, when set in an ebuild, > will serve to indicate that the ebuild will use some form of "live" > source code that may vary each time that the package is installed. > The intention is for PROPERTIES=live to have a relatively pure and > simple meaning. Therefore, the definition is intentionally more > narrow than the definitions previously suggested for the related > RESTRICT=live [1] and PROPERTIES=live-sources [2] values. In the > future we may add additional (orthogonal) properties to represent > other things like locking [3].
Here's what I'd like to see from this whole PROPERTIES discussion. - Are the PROPERTIES more fine-grained than they need to be? - Are the common use cases specifiable by a single PROPERTIES setting that may actually do multiple things on the back end? If there's actually reasons for these things to be very narrow, I'd like to see easily usable meta-properties that let people easily say something like "I've got a live CVS ebuild" without specifying 20 different PROPERTIES. -- Thanks, Donnie Donnie Berkholz Developer, Gentoo Linux Blog: http://dberkholz.wordpress.com
pgpMMyb7L33ja.pgp
Description: PGP signature
