[gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Andreas K. Huettel]

[-- Attachment #1: Type: text/plain, Size: 1583 bytes --]


For general review and improvement, to be committed 2013-09-25...
[The summary link [3] will work soon... :) ]

##################

Title: m68k, s390, and sh are dropping stable keywords                                                                                                                                     
Author: Andreas K. Huettel <dilfridge@gentoo.org>
Content-Type: text/plain
Posted: 2013-09-25
Revision: 1
News-Item-Format: 1.0
Display-If-Keyword: m68k
Display-If-Keyword: s390
Display-If-Keyword: sh

Following discussion [1] and a vote by the Gentoo Council [2,3], 
m68k, s390, and sh will drop all stable keywords and become 
unstable/testing only arches. The main reason for this is that 
these arch teams visibly lack manpower, leading to overall delays.
Stable may well be synonymous with outdated here.

In a week, the ACCEPT_KEYWORDS variable in the respective profiles
will be switched to automatically include ~arch packages. Systems
running stable before will update to current unstable/testing then.
Afterwards m68k, s390, and sh keywords on all ebuilds will be
changed to ~m68k, ~s390, and ~sh.

No steps are required from users, however you should be aware
of the upcoming changes.

[1] http://thread.gmane.org/gmane.linux.gentoo.project/2975/focus=2984
[2] http://www.gentoo.org/proj/en/council/meeting-logs/20130917.txt
[3] http://www.gentoo.org/proj/en/council/meeting-logs/20130917-summary.txt


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

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Tom Wijsman]

[-- Attachment #1: Type: text/plain, Size: 690 bytes --]

On Thu, 19 Sep 2013 21:29:35 +0200
"Andreas K. Huettel" <dilfridge@gentoo.org> wrote:

> Title: m68k, s390, and sh are dropping stable keywords

Please note that this is longer than the GLEP 42 specification [1],
which mentions a short (maximum 44 characters) descriptive title.

"m68k, s390, and sh are dropping stable keywords".length = 47

The news article is clear, reads fine; I don't see any other problems.

 [1]: http://www.gentoo.org/proj/en/glep/glep-0042.html

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Pacho Ramos]

What should we do with pending stabilization bugs having this arches
CCed? unCC them?

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Andreas K. Huettel]

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

Am Donnerstag, 19. September 2013, 21:49:36 schrieb Pacho Ramos:
> What should we do with pending stabilization bugs having this arches
> CCed? unCC them?

Not sure... seems logical though...

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

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Aaron W. Swenson]

[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]

On 2013-09-19 21:29, Andreas K. Huettel wrote:
>
> For general review and improvement, to be committed 2013-09-25...
> [The summary link [3] will work soon... :) ]
>
> ##################
>
> Title: m68k, s390, and sh are dropping stable keywords

To stay within 42 characters, perhaps rewrite the title as:
   Drop Stable Keyword for m68k, s390, and sh

Or:
    m68k, s390, and sh Move to Unstable

> ...
>
> Following discussion [1] and a vote by the Gentoo Council [2,3],
> m68k, s390, and sh will drop all stable keywords and become
> unstable/testing only arches. The main reason for this is that
> these arch teams visibly lack manpower, leading to overall delays.
> Stable may well be synonymous with outdated here.

I would remove the last sentence. It read a bit as
editorializing. However, I'd change "leading to overall delays" to
"which resulted in undesirable delays".

> ...
>
> No steps are required from users, however you should be aware
> of the upcoming changes.

I'd "bottom line" this as:
    No action is required to prepare for this change.

Of course, just my 2¢.

--
Mr. Aaron W. Swenson
Gentoo Linux Developer
PostgreSQL Herd Bull
Email : titanofold@gentoo.org
GnuPG FP : 2C00 7719 4F85 FB07 A49C 0E31 5713 AA03 D1BB FDA0
GnuPG ID : D1BBFDA0

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]

[gentoo-dev] Re: News item: m68k, s390, and sh are dropping stable keywords

[Duncan]

Aaron W. Swenson posted on Thu, 19 Sep 2013 20:36:50 +0000 as excerpted:

> On 2013-09-19 21:29, Andreas K. Huettel wrote:
>>
>> For general review and improvement, to be committed 2013-09-25... [The
>> summary link [3] will work soon... :) ]
>>
>> ##################
>>
>> Title: m68k, s390, and sh are dropping stable keywords
> 
> To stay within 42 characters, perhaps rewrite the title as:
>    Drop Stable Keyword for m68k, s390, and sh
> 
> Or:
>     m68k, s390, and sh Move to Unstable

Or even just drop "and" and replacing "are" with a colon (assuming a 
colon is allowed):

m68k, s390, sh: Dropping stable keywords

>> Following discussion [1] and a vote by the Gentoo Council [2,3], m68k,
>> s390, and sh will drop all stable keywords and become unstable/testing
>> only arches. The main reason for this is that these arch teams visibly
>> lack manpower, leading to overall delays.
>> Stable may well be synonymous with outdated here.
> 
> I would remove the last sentence. It read a bit as editorializing.
> However, I'd change "leading to overall delays" to "which resulted in
> undesirable delays".

Or "resulting in undesirable delays."

But remembering this is targeted at users, I'd keep but change the last 
sentence as well, as "outdated" or more specifically "insecure" is likely 
to be the big user-viewpoint concern that this should address.

"The concern is that stable thus risked being synonymous with dated and 
possibly insecure, such that dropping it seemed the best and most 
practical way forward."

But dropping the sentence entirely works too; I just think users might be 
left wondering why they can't simply keep existing stable only and not 
update, and this sentence makes explicit the ultimate risk in that.  But 
perhaps that explicitness isn't necessary.

>> No steps are required from users, however you should be aware of the
>> upcoming changes.
> 
> I'd "bottom line" this as:
>     No action is required to prepare for this change.
> 
> Of course, just my 2¢.

"This notice is for information only.  No user action required."

... And that could either remain at the bottom, or be moved to be the 
first paragraph.

Talking about which... perhaps making it a general practice to make the 
first sentence/paragraph either "notice only", or "user action required", 
would be a good idea?  Maybe even promote it to a general header
("Action status: Notice only", "Action status: Action required" ?), so 
readers/tools that wish to can sort by it?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Andreas K. Huettel]

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

And committed.

-------

Title: m68k, s390, sh are dropping stable keywords                                                                                                                                     
Author: Andreas K. Huettel <dilfridge@gentoo.org>
Content-Type: text/plain
Posted: 2013-09-22
Revision: 1
News-Item-Format: 1.0
Display-If-Keyword: m68k
Display-If-Keyword: s390
Display-If-Keyword: sh

Following discussion [1] and a vote by the Gentoo Council [2,3], 
m68k, s390, and sh will drop all stable keywords and become 
unstable/testing only arches. The main reason for this is that 
these arch teams visibly lack manpower, resulting in undesirable
delays.

In a week, the ACCEPT_KEYWORDS variable in the respective profiles
will be switched to automatically include ~arch packages. Systems
running stable before will update to current unstable/testing then.
Afterwards m68k, s390, and sh keywords on all ebuilds will be
changed to ~m68k, ~s390, and ~sh.

No steps are required from users, however you should be aware
of the upcoming changes.

[1] http://thread.gmane.org/gmane.linux.gentoo.project/2975/focus=2984
[2] http://www.gentoo.org/proj/en/council/meeting-logs/20130917.txt
[3] http://www.gentoo.org/proj/en/council/meeting-logs/20130917-summary.txt



Am Donnerstag, 19. September 2013, 21:29:35 schrieb Andreas K. Huettel:
> For general review and improvement, to be committed 2013-09-25...
> [The summary link [3] will work soon... :) ]
> 


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

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Jack Morgan]

[-- Attachment #1: Type: text/plain, Size: 1932 bytes --]

On Sun, Sep 22, 2013 at 10:38:57AM +0200, Andreas K. Huettel wrote:
> And committed.
> 
> -------
> 
> Title: m68k, s390, sh are dropping stable keywords                                                                                                                                     
> Author: Andreas K. Huettel <dilfridge@gentoo.org>
> Content-Type: text/plain
> Posted: 2013-09-22
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Keyword: m68k
> Display-If-Keyword: s390
> Display-If-Keyword: sh
> 
> Following discussion [1] and a vote by the Gentoo Council [2,3], 
> m68k, s390, and sh will drop all stable keywords and become 
> unstable/testing only arches. The main reason for this is that 
> these arch teams visibly lack manpower, resulting in undesirable
> delays.

Please remove the word "unstable" as there are no "unstable" keywords in
Gentoo Linux, just stable and testing. 

> In a week, the ACCEPT_KEYWORDS variable in the respective profiles
> will be switched to automatically include ~arch packages. Systems
> running stable before will update to current unstable/testing then.
> Afterwards m68k, s390, and sh keywords on all ebuilds will be
> changed to ~m68k, ~s390, and ~sh.
> 
> No steps are required from users, however you should be aware
> of the upcoming changes.
> 
> [1] http://thread.gmane.org/gmane.linux.gentoo.project/2975/focus=2984
> [2] http://www.gentoo.org/proj/en/council/meeting-logs/20130917.txt
> [3] http://www.gentoo.org/proj/en/council/meeting-logs/20130917-summary.txt
> 
> 
> 
> Am Donnerstag, 19. September 2013, 21:29:35 schrieb Andreas K. Huettel:
> > For general review and improvement, to be committed 2013-09-25...
> > [The summary link [3] will work soon... :) ]
> > 


Thanks,
-- 
Jack Morgan
Pub 4096R/761D8E0A 2010-09-13 Jack Morgan <jmorgan@gentoo.org>>
Fingerprint = DD42 EA48 D701 D520 C2CD 55BE BF53 C69B 761D 8E0A

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Samuli Suominen]

[ ... ]

Stealing random mail from this thread.

Because I've seen some commits today for reverting the mentioned 
KEYWORDS to ~arch in some ebuilds I'm not sure if everyone is aware that 
the arch status is set using profiles/profiles.desc and as I'm writing 
this, the mentioned arches are still 'stable', not 'dev'
No matter what the news item or whatever says, only profiles.desc counts

- Samuli

[gentoo-dev] Re: News item: m68k, s390, and sh are dropping stable keywords

[Michael Palimaka]

On 23/09/2013 21:34, Samuli Suominen wrote:
> [ ... ]
>
> Stealing random mail from this thread.
>
> Because I've seen some commits today for reverting the mentioned
> KEYWORDS to ~arch in some ebuilds I'm not sure if everyone is aware that
> the arch status is set using profiles/profiles.desc and as I'm writing
> this, the mentioned arches are still 'stable', not 'dev'
> No matter what the news item or whatever says, only profiles.desc counts
>
> - Samuli
>
>
Didn't dev profiles cause issues with prefix profiles due to repoman not 
reporting unresolved dependencies?

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Ulrich Mueller]

>>>>> On Mon, 23 Sep 2013, Samuli Suominen wrote:

> Because I've seen some commits today for reverting the mentioned 
> KEYWORDS to ~arch in some ebuilds I'm not sure if everyone is aware that 
> the arch status is set using profiles/profiles.desc and as I'm writing 
> this, the mentioned arches are still 'stable', not 'dev'
> No matter what the news item or whatever says, only profiles.desc counts

That's a thing that was never quite clear to me. Should there be
a one-to-one correspondence between an arch marked stable in
profiles.desc (i.e. having at least one profile labelled as stable
there) and the same arch having stable keywords?

There is at least one example for an arch that is only dev in
profiles.desc but used to have stable keywords (sh), and another arch
where it's the other way around (amd64-fbsd).

Ulrich

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Samuli Suominen]

On 23/09/13 15:52, Ulrich Mueller wrote:
>>>>>> On Mon, 23 Sep 2013, Samuli Suominen wrote:
>
>> Because I've seen some commits today for reverting the mentioned
>> KEYWORDS to ~arch in some ebuilds I'm not sure if everyone is aware that
>> the arch status is set using profiles/profiles.desc and as I'm writing
>> this, the mentioned arches are still 'stable', not 'dev'
>> No matter what the news item or whatever says, only profiles.desc counts
>
> That's a thing that was never quite clear to me. Should there be
> a one-to-one correspondence between an arch marked stable in
> profiles.desc (i.e. having at least one profile labelled as stable
> there) and the same arch having stable keywords?

of course...

> There is at least one example for an arch that is only dev in
> profiles.desc but used to have stable keywords (sh), and another arch
> where it's the other way around (amd64-fbsd).
>
> Ulrich
>

can't believe it was like that for amd64-fbsd and nobody noticed before, 
fixed that.

i'm a bit confused, why do you think sh is not an stable arch?
it's still an stable arch like m68k and s390 is... until someone changes 
those lines as per council's vote.

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Samuli Suominen]

On 23/09/13 16:08, Samuli Suominen wrote:
> On 23/09/13 15:52, Ulrich Mueller wrote:
>>>>>>> On Mon, 23 Sep 2013, Samuli Suominen wrote:
>>
>>> Because I've seen some commits today for reverting the mentioned
>>> KEYWORDS to ~arch in some ebuilds I'm not sure if everyone is aware that
>>> the arch status is set using profiles/profiles.desc and as I'm writing
>>> this, the mentioned arches are still 'stable', not 'dev'
>>> No matter what the news item or whatever says, only profiles.desc counts
>>
>> That's a thing that was never quite clear to me. Should there be
>> a one-to-one correspondence between an arch marked stable in
>> profiles.desc (i.e. having at least one profile labelled as stable
>> there) and the same arch having stable keywords?
>
> of course...
>
>> There is at least one example for an arch that is only dev in
>> profiles.desc but used to have stable keywords (sh), and another arch
>> where it's the other way around (amd64-fbsd).
>>
>> Ulrich
>>
> i'm a bit confused, why do you think sh is not an stable arch?
> it's still an stable arch like m68k and s390 is... until someone changes
> those lines as per council's vote.

ah, scratch that, got it now -- vapier already started downgrading the 
'sh' status earlier, before the council's vote by changing the profiles.desc

[gentoo-dev] Re: News item: m68k, s390, and sh are dropping stable keywords

[Michael Palimaka]

On 23/09/2013 22:52, Ulrich Mueller wrote:
>>>>>> On Mon, 23 Sep 2013, Samuli Suominen wrote:
>
>> Because I've seen some commits today for reverting the mentioned
>> KEYWORDS to ~arch in some ebuilds I'm not sure if everyone is aware that
>> the arch status is set using profiles/profiles.desc and as I'm writing
>> this, the mentioned arches are still 'stable', not 'dev'
>> No matter what the news item or whatever says, only profiles.desc counts
>
> That's a thing that was never quite clear to me. Should there be
> a one-to-one correspondence between an arch marked stable in
> profiles.desc (i.e. having at least one profile labelled as stable
> there) and the same arch having stable keywords?
In my opinion the two need not be linked. To me "profile stability" 
refers to the status of the profile, nothing to do with keywords.

If an arch team does not want to maintain stable keywords, but wants to 
indicate that a particular profile is stable, why should we try to stop 
them?

Re: [gentoo-dev] Re: News item: m68k, s390, and sh are dropping stable keywords

[Dirkjan Ochtman]

On Mon, Sep 23, 2013 at 3:18 PM, Michael Palimaka <kensington@gentoo.org> wrote:
>> That's a thing that was never quite clear to me. Should there be
>> a one-to-one correspondence between an arch marked stable in
>> profiles.desc (i.e. having at least one profile labelled as stable
>> there) and the same arch having stable keywords?
>
> In my opinion the two need not be linked. To me "profile stability" refers
> to the status of the profile, nothing to do with keywords.
>
> If an arch team does not want to maintain stable keywords, but wants to
> indicate that a particular profile is stable, why should we try to stop
> them?

What does eshowkw use to determine what arches should be displayed?

Cheers,

Dirkjan

Re: [gentoo-dev] Re: News item: m68k, s390, and sh are dropping stable keywords

[Samuli Suominen]

On 23/09/13 16:18, Michael Palimaka wrote:
> On 23/09/2013 22:52, Ulrich Mueller wrote:
>>>>>>> On Mon, 23 Sep 2013, Samuli Suominen wrote:
>>
>>> Because I've seen some commits today for reverting the mentioned
>>> KEYWORDS to ~arch in some ebuilds I'm not sure if everyone is aware that
>>> the arch status is set using profiles/profiles.desc and as I'm writing
>>> this, the mentioned arches are still 'stable', not 'dev'
>>> No matter what the news item or whatever says, only profiles.desc counts
>>
>> That's a thing that was never quite clear to me. Should there be
>> a one-to-one correspondence between an arch marked stable in
>> profiles.desc (i.e. having at least one profile labelled as stable
>> there) and the same arch having stable keywords?
> In my opinion the two need not be linked. To me "profile stability"
> refers to the status of the profile, nothing to do with keywords.
>
> If an arch team does not want to maintain stable keywords, but wants to
> indicate that a particular profile is stable, why should we try to stop
> them?

profiles.desc status is about how repoman is used to scan KEYWORDS, and 
those arch maintainers with only ~arch keywording use `repoman 
--include-dev` so changing the status from 'dev' to 'stable' won't gain 
anything scanning wise

unless we are discussing changing the repoman's default to include the 
dev profiles in the scan, and exclude them by might-be switch like 
--without-dev?

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Samuli Suominen]

On 23/09/13 16:08, Samuli Suominen wrote:
> can't believe it was like that for amd64-fbsd and nobody noticed before,
> fixed that.

scratch that too. left it at dev.
if the entire tree is fine with some arch being at ~ and no dependencies 
are broken, that could counted as 'stable' too.
then setting it from 'dev' to 'stable' will just make sure nobody breaks 
the perfect record of no dependencies broken.

it might be useful to have another status added to the profiles.desc for 
that case, like 'semi-stable' or whatever since amd64-fbsd might not fit 
either, 'dev' or 'stable' :/

Re: [gentoo-dev] Re: News item: m68k, s390, and sh are dropping stable keywords

[Alexis Ballier]

On Mon, 23 Sep 2013 16:25:40 +0300
Samuli Suominen <ssuominen@gentoo.org> wrote:

> profiles.desc status is about how repoman is used to scan KEYWORDS,
> and those arch maintainers with only ~arch keywording use `repoman 
> --include-dev` so changing the status from 'dev' to 'stable' won't
> gain anything scanning wise

not entirely true: repoman is for _every_ dev.
facts are explained here:
http://article.gmane.org/gmane.linux.gentoo.devel/76909

in practice, profiles.desc and arch/~arch are orthogonal.

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Ulrich Mueller]

>>>>> On Mon, 23 Sep 2013, Samuli Suominen wrote:

> if the entire tree is fine with some arch being at ~ and no dependencies 
> are broken, that could counted as 'stable' too.
> then setting it from 'dev' to 'stable' will just make sure nobody breaks 
> the perfect record of no dependencies broken.

The problem with that is that we don't track the keyword status of an
arch anywhere in profiles, so tools like ekeyword or ebuild-mode in
Emacs have no way of obtaining that information (other than hardcoding
it).

We tried to rectify the situation in bug 304133, but it didn't work out.

> it might be useful to have another status added to the profiles.desc for 
> that case, like 'semi-stable' or whatever since amd64-fbsd might not fit 
> either, 'dev' or 'stable' :/

Either that, or add another file to the profiles dir.

Ulrich

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Alexis Ballier]

On Mon, 23 Sep 2013 15:57:48 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:

> >>>>> On Mon, 23 Sep 2013, Samuli Suominen wrote:
> 
> > if the entire tree is fine with some arch being at ~ and no
> > dependencies are broken, that could counted as 'stable' too.
> > then setting it from 'dev' to 'stable' will just make sure nobody
> > breaks the perfect record of no dependencies broken.
> 
> The problem with that is that we don't track the keyword status of an
> arch anywhere in profiles, so tools like ekeyword or ebuild-mode in
> Emacs have no way of obtaining that information (other than hardcoding
> it).

we do track it with ACCEPT_KEYWORDS

either way, in comparison to having broken deps coming out of the wild,
this is very minor imho: 'ekeyword all' is a bit doubtful, and I assume
emacs uses this to color differently variables in KEYWORDS


[...]
> > it might be useful to have another status added to the
> > profiles.desc for that case, like 'semi-stable' or whatever since
> > amd64-fbsd might not fit either, 'dev' or 'stable' :/
> 
> Either that, or add another file to the profiles dir.

we have 'stable', 'dev' and 'exp'; the difference between 'dev' and
'exp' is unclear to me. it could be changed so that broken deps in
'dev' profiles are a repoman error (without -d) but without stable
keywords.

Alexis.

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Ulrich Mueller]

>>>>> On Mon, 23 Sep 2013, Alexis Ballier wrote:

>> The problem with that is that we don't track the keyword status of an
>> arch anywhere in profiles, so tools like ekeyword or ebuild-mode in
>> Emacs have no way of obtaining that information (other than hardcoding
>> it).

> we do track it with ACCEPT_KEYWORDS

Yeah, but that's scattered all over the place and not easily
accessible, without fully resolving all interdependencies between
profiles.

   $ grep -lr ACCEPT_KEYWORDS /usr/portage/profiles | wc -l
   99

Ulrich

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Alexis Ballier]

On Mon, 23 Sep 2013 16:23:35 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:

> >>>>> On Mon, 23 Sep 2013, Alexis Ballier wrote:
> 
> >> The problem with that is that we don't track the keyword status of
> >> an arch anywhere in profiles, so tools like ekeyword or
> >> ebuild-mode in Emacs have no way of obtaining that information
> >> (other than hardcoding it).
> 
> > we do track it with ACCEPT_KEYWORDS
> 
> Yeah, but that's scattered all over the place and not easily
> accessible, without fully resolving all interdependencies between
> profiles.
> 
>    $ grep -lr ACCEPT_KEYWORDS /usr/portage/profiles | wc -l
>    99

it could be 'fixed' by kindly asking and moving ACCEPT_KEYWORDS
setting to the 'advertised profile', that is in ${dir}/make.defaults
where ${dir} is the directory listed in profiles.desc

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Markos Chandras]

On 09/23/2013 03:07 PM, Alexis Ballier wrote:
> 
> we have 'stable', 'dev' and 'exp'; the difference between 'dev' and
> 'exp' is unclear to me. it could be changed so that broken deps in
> 'dev' profiles are a repoman error (without -d) but without stable
> keywords.
> 
> Alexis.
> 
I believe the 'exp' profile makes no sense. It might did in the past,
but I believe we are fine having only 'stable' and 'dev'. So unless I am
missing something obvious, 'dev' can be used to express ~arch only
architectures whether they are in a good or bad state.

-- 
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang

Re: [gentoo-dev] Re: News item: m68k, s390, and sh are dropping stable keywords

[Markos Chandras]

On 09/23/2013 02:46 PM, Alexis Ballier wrote:
> On Mon, 23 Sep 2013 16:25:40 +0300
> Samuli Suominen <ssuominen@gentoo.org> wrote:
> 
>> profiles.desc status is about how repoman is used to scan KEYWORDS,
>> and those arch maintainers with only ~arch keywording use `repoman 
>> --include-dev` so changing the status from 'dev' to 'stable' won't
>> gain anything scanning wise
> 
> not entirely true: repoman is for _every_ dev.
> facts are explained here:
> http://article.gmane.org/gmane.linux.gentoo.devel/76909
> 
> in practice, profiles.desc and arch/~arch are orthogonal.
> 

Yes in practice they are orthogonal. One could argue that all profiles
should be marked 'stable' in order to improve the overall dependency
coverage and stability because, lets face it, very few devs run repoman -d.

-- 
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang

Re: [gentoo-dev] News item: m68k, s390, and sh are dropping stable keywords

[Sergey Popov]

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

23.09.2013 22:29, Markos Chandras пишет:
> On 09/23/2013 03:07 PM, Alexis Ballier wrote:
>>
>> we have 'stable', 'dev' and 'exp'; the difference between 'dev' and
>> 'exp' is unclear to me. it could be changed so that broken deps in
>> 'dev' profiles are a repoman error (without -d) but without stable
>> keywords.
>>
>> Alexis.
>>
> I believe the 'exp' profile makes no sense. It might did in the past,
> but I believe we are fine having only 'stable' and 'dev'. So unless I am
> missing something obvious, 'dev' can be used to express ~arch only
> architectures whether they are in a good or bad state.
> 

I think current dedication of pure-unstable arches on well-maintained
and dependency consistent arches in dev and arches where dependency
consistency is someway broken(Prefix) makes sense.

Unless somebody wants to clean up some mess i have seen in Prefix deps
by fulling package.use.mask in prefix profiles with tons of deps.

Anyway, we have apropriate options in repoman for checking on dev and
exp profiles, and, regarding the Prefix, i think we can try to move
prefix profiles to dev when Prefix tree will be merged with gentoo-x86

-- 
Best regards, Sergey Popov
Gentoo developer
Gentoo Desktop Effects project lead
Gentoo Qt project lead
Gentoo Proxy maintainers project lead


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]