[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] [RFC] PROPERTIES=live (instead of	PROPERTIES=live-sources
From:       Zac Medico <zmedico () gentoo ! org>
Date:       2008-08-25 17:46:50
Message-ID: 48B2F00A.2080804 () gentoo ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Donnie Berkholz wrote:
> 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?

Sure, we can add addition properties that have compound meanings.
However, I'm pretty satisfied with the "pure and simple" form that
I've suggested for the live, virtual, and interactive properties.
Their purity makes them narrow in a way, but also broad in the sense
that they will usable for a maximum number of ebuilds without any
deviation from the official meaning.

> 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.

For a cases like this, we can define a "live-cvs" property that
implies the "live" property. By defining compound properties in this
way, we can avoid things like PROPERTIES="live live-cvs" since
"live-cvs" alone will also imply "live". As such, it would be
redundant to set PROPERTIES="live live-cvs" when
PROPERTIES="live-cvs" would have identical meaning.
- --
Thanks,
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkiy8AgACgkQ/ejvha5XGaOnuQCg7up9Pw0nIgtg8GvKgTj2KHKn
VKwAoJ5xfKpaYEn8Z5u1ly7ELHoh+t3N
=4tZZ
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]