[gentoo-dev] repoman feature request / profiles.desc profile types

[gentoo-dev] repoman feature request / profiles.desc profile types

[Andreas K. Huettel]

[-- Attachment #1: Type: Text/Plain, Size: 925 bytes --]


Hi all, 

Right now we have arches maintaining a stable keyword and we have arches that 
don't do that.

This makes me think that the classification of profiles as "exp", "dev", 
"stable" in profiles.desc does not really cover all usecases. 

[Current meaning: 
"stable" - repoman checks it, arch has stable keyword
"dev" - repoman checks it with -d
"exp" - repoman ignores it]

I'd like to propose two additional profile types:
"nonstable" - repoman checks it, arch has no stable keyword (and if there is 
one in an ebuild, repoman treats it as arch=~arch)
"dev-nonstable" - repoman checks it with -d, arch has no stable keyword (and 
if there is one in an ebuild, repoman treats it as arch=~arch)

Why not make it possible to keep an ~arch only deptree consistent?!

Cheers, 
Andreas

-- 
Andreas K. Huettel
Gentoo Linux developer (council, kde)
dilfridge@gentoo.org
http://www.akhuettel.de/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[gentoo-dev] Re: repoman feature request / profiles.desc profile types

[Michael Palimaka]

On 02/17/2014 03:58 AM, Andreas K. Huettel wrote:
> Why not make it possible to keep an ~arch only deptree consistent?!

amd64-fbsd already does this with a stable profile. They just choose to
not actually have any stable keywords.
In my opinion, the profile type is better as a description of that
profile, rather than a signifier of what keywords are permitted.

Re: [gentoo-dev] Re: repoman feature request / profiles.desc profile types

[Andreas K. Huettel]

[-- Attachment #1: Type: Text/Plain, Size: 646 bytes --]

Am Sonntag, 16. Februar 2014, 18:18:56 schrieb Michael Palimaka:
> On 02/17/2014 03:58 AM, Andreas K. Huettel wrote:
> > Why not make it possible to keep an ~arch only deptree consistent?!
> 
> amd64-fbsd already does this with a stable profile. They just choose to
> not actually have any stable keywords.
> In my opinion, the profile type is better as a description of that
> profile, rather than a signifier of what keywords are permitted.

I agree with that, but that's not how it was historically used / intended to 
be used.

-- 

Andreas K. Huettel
Gentoo Linux developer 
dilfridge@gentoo.org
http://www.akhuettel.de/


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 966 bytes --]

[gentoo-dev] Re: repoman feature request / profiles.desc profile types

[Michael Palimaka]

On 02/17/2014 05:36 AM, Andreas K. Huettel wrote:
> Am Sonntag, 16. Februar 2014, 18:18:56 schrieb Michael Palimaka:
>> On 02/17/2014 03:58 AM, Andreas K. Huettel wrote:
>>> Why not make it possible to keep an ~arch only deptree consistent?!
>>
>> amd64-fbsd already does this with a stable profile. They just choose to
>> not actually have any stable keywords.
>> In my opinion, the profile type is better as a description of that
>> profile, rather than a signifier of what keywords are permitted.
> 
> I agree with that, but that's not how it was historically used / intended to 
> be used.
> 

Let's change the historical meaning then - it really doesn't stray too
far from the existing documented policy[1]. :-)

In my opinion the change more accurately reflects reality. Profile
status has no actual effect on keywords (that policy is set and
self-enforced by arch teams anyway), but does affect how repoman checks it.

[1]: http://devmanual.gentoo.org/profiles/profiles.desc/index.html

Re: [gentoo-dev] repoman feature request / profiles.desc profile types

[Alexis Ballier]

On Sun, 16 Feb 2014 17:58:39 +0100
"Andreas K. Huettel" <dilfridge@gentoo.org> wrote:

> 
> Hi all, 
> 
> Right now we have arches maintaining a stable keyword and we have
> arches that don't do that.
> 
> This makes me think that the classification of profiles as "exp",
> "dev", "stable" in profiles.desc does not really cover all usecases. 
> 
> [Current meaning: 
> "stable" - repoman checks it, arch has stable keyword
> "dev" - repoman checks it with -d
> "exp" - repoman ignores it]
> 
> I'd like to propose two additional profile types:
> "nonstable" - repoman checks it, arch has no stable keyword (and if
> there is one in an ebuild, repoman treats it as arch=~arch)
> "dev-nonstable" - repoman checks it with -d, arch has no stable
> keyword (and if there is one in an ebuild, repoman treats it as
> arch=~arch)

+1

(dev-nonstable isnt really appealing as history has proved that nobody
dares to check deptree for dev/exp profiles)

> Why not make it possible to keep an ~arch only deptree consistent?!

it is possible, there's just a lot of confusion around it :)
this "cosmetic" change should really help in avoiding this confusion


Alexis.