[gentoo-dev] Remove "dev"-status of mips profiles

[gentoo-dev] Remove "dev"-status of mips profiles

[Torsten Veller]

Can we please move the mips profiles from "dev" to "exp" in
profiles/profiles.desc?


The ~150 mips development profiles increase the time for a 
`repoman -d full` run in dev-perl/ from three to five minutes. That is
an increase of roughly 66 percent.
repoman further prints more than 2000 lines of output for two keywording
problems.

I can't remember any serious mips keywording activity in the last years.
I don't see why I should spend any more time on checking their profiles
and filing bugs for an unactive team.


Open KEYWORDREQ bugs:
https://bugs.gentoo.org/buglist.cgi?quicksearch=kw%3AKEYWORDREQ+owner%2Ccc%3Amips%40gentoo.org

[gentoo-dev] Re: Remove "dev"-status of mips profiles

[Christian Faulhammer]

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

Hi,

Torsten Veller <tove@gentoo.org>:

> Can we please move the mips profiles from "dev" to "exp" in
> profiles/profiles.desc?

 Agreement here.  Maybe a restart on non-obsolete MIPS hardware (read
Loongson instead of SGI) would be great.

V-Li	

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://gentoo.faulhammer.org/>

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

Re: [gentoo-dev] Remove "dev"-status of mips profiles

[Brian Harring]

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

On Thu, Feb 11, 2010 at 04:54:38PM +0100, Torsten Veller wrote:
> Can we please move the mips profiles from "dev" to "exp" in
> profiles/profiles.desc?
> 
> 
> The ~150 mips development profiles increase the time for a 
> `repoman -d full` run in dev-perl/ from three to five minutes. That is
> an increase of roughly 66 percent.
> repoman further prints more than 2000 lines of output for two keywording
> problems.

Quick pcheck visibility scan of the full tree, stats follow:

mips profiles still enabled:
* 116191 seperate dependency issues, 1 line per profile/dependency 
  issue
* roughly 2m39s run time

mips profiles disabled (leaving mips-irix however)
* 9550 seperate dependency issues, 1 line per profile/dependency issue
* roughly 1m54s run time.

So... mips accounts for about 30% of the pcheck runtime, and *92%* of 
known visibility issues.  As for the runtime difference between 
pcheck/repoman, pcheck has some tricks internally to reduce the # of 
profiles it has to scan down to just the unique USE/mask set- I'd 
expect the mips impact to be far larger w/out that trick in place.

At the very least if it's going to be kept around, experimental or 
not, the number of profiles in use there *really* needs reduction- 
mips has roughly 117 profiles listed in profiles.desc out of 217- 
literally ~54%  of all dev/stable/experimental profiles.

Either way, stats to chew on.
~harring

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

Re: [gentoo-dev] Remove "dev"-status of mips profiles

[Jeremy Olexa]

On Thu, 11 Feb 2010 10:41:41 -0800, Brian Harring <ferringb@gmail.com>
wrote:
> On Thu, Feb 11, 2010 at 04:54:38PM +0100, Torsten Veller wrote:
>> Can we please move the mips profiles from "dev" to "exp" in
>> profiles/profiles.desc?
>> 
>> 
>> The ~150 mips development profiles increase the time for a 
>> `repoman -d full` run in dev-perl/ from three to five minutes. That is
>> an increase of roughly 66 percent.
>> repoman further prints more than 2000 lines of output for two
keywording
>> problems.
> 
> Quick pcheck visibility scan of the full tree, stats follow:
> 
> mips profiles still enabled:
> * 116191 seperate dependency issues, 1 line per profile/dependency 
>   issue
> * roughly 2m39s run time
> 
> mips profiles disabled (leaving mips-irix however)
> * 9550 seperate dependency issues, 1 line per profile/dependency issue
> * roughly 1m54s run time.
> 
> So... mips accounts for about 30% of the pcheck runtime, and *92%* of 
> known visibility issues.  As for the runtime difference between 
> pcheck/repoman, pcheck has some tricks internally to reduce the # of 
> profiles it has to scan down to just the unique USE/mask set- I'd 
> expect the mips impact to be far larger w/out that trick in place.
> 
> At the very least if it's going to be kept around, experimental or 
> not, the number of profiles in use there *really* needs reduction- 
> mips has roughly 117 profiles listed in profiles.desc out of 217- 
> literally ~54%  of all dev/stable/experimental profiles.

I agree, I wasn't sure why so many profiles were added[1] for a dead team
(for all intensive purposes). Seems quite silly to me to leave them as
'dev' status. If a member of the mips team would reply to this thread, that
would be good. (and surprising to me :)

I would guess that it would be far easier to work in an overlay at this
point. I would also guess that if there are ANY mips users out there that
they would have to use some other ACCEPT_KEYWORDS value because the shape
of ~mips is so...bad.
-Jeremy

[1]:
http://sources.gentoo.org/viewcvs.py/gentoo-x86/profiles/profiles.desc?r1=1.151&r2=1.152

> 
> Either way, stats to chew on.
> ~harring

Re: [gentoo-dev] Remove "dev"-status of mips profiles

[Brian Harring]

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

On Thu, Feb 11, 2010 at 06:56:58PM +0000, Jeremy Olexa wrote:
> I would guess that it would be far easier to work in an overlay at this
> point. I would also guess that if there are ANY mips users out there that
> they would have to use some other ACCEPT_KEYWORDS value because the shape
> of ~mips is so...bad.

Might want to wait till the cvs->git transition occurs, assuming it's 
in the next few months- primarily, preserve history, they can just 
fork the tree off and mainline can start pruning.

Till then the profiles could pretty easily be disabled if folks 
wanted.
~harring

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

Re: [gentoo-dev] Remove "dev"-status of mips profiles

[Brian Harring]

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

On Thu, Feb 11, 2010 at 06:56:58PM +0000, Jeremy Olexa wrote:
> > At the very least if it's going to be kept around, experimental or 
> > not, the number of profiles in use there *really* needs reduction- 
> > mips has roughly 117 profiles listed in profiles.desc out of 217- 
> > literally ~54%  of all dev/stable/experimental profiles.

Correction also- they've got 154 rather than 117, meaning 71% of 
all profiles for a scan.

Not sure how I screwed that number up, but aparently I managed it.
~harring

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

Re: [gentoo-dev] Remove "dev"-status of mips profiles

[Samuli Suominen]

On 02/11/2010 08:56 PM, Jeremy Olexa wrote:
>>> Can we please move the mips profiles from "dev" to "exp" in
>>> profiles/profiles.desc?
>>> The ~150 mips development profiles increase the time for a 
>>> `repoman -d full` run in dev-perl/ from three to five minutes. That is
>>> an increase of roughly 66 percent.
>>> repoman further prints more than 2000 lines of output for two
> keywording
>>> problems.
>>
>> Quick pcheck visibility scan of the full tree, stats follow:
>>
>> mips profiles still enabled:
>> * 116191 seperate dependency issues, 1 line per profile/dependency 
>>   issue
>> * roughly 2m39s run time
>>
>> mips profiles disabled (leaving mips-irix however)
>> * 9550 seperate dependency issues, 1 line per profile/dependency issue
>> * roughly 1m54s run time.

[ .. ]

> 
> [1]:
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/profiles/profiles.desc?r1=1.151&r2=1.152

We could at least delete the server/desktop/developer profiles from the
above list right away, not really required to have them for every
machine type IMHO

[gentoo-dev] Re: Remove "dev"-status of mips profiles

[Christian Faulhammer]

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

Hi,

Jeremy Olexa <darkside@gentoo.org>:
> I would guess that it would be far easier to work in an overlay at
> this point. I would also guess that if there are ANY mips users out
> there that they would have to use some other ACCEPT_KEYWORDS value
> because the shape of ~mips is so...bad.

 Don't remove an architecture.  Ask vapier what it means to reintroduce
it.  Even if it rots, mark it as unmaintained and wait for someone to
pick-up.

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://gentoo.faulhammer.org/>

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

Re: [gentoo-dev] Re: Remove "dev"-status of mips profiles

[Brian Harring]

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

On Thu, Feb 11, 2010 at 10:12:44PM +0100, Christian Faulhammer wrote:
> Hi,
> 
> Jeremy Olexa <darkside@gentoo.org>:
> > I would guess that it would be far easier to work in an overlay at
> > this point. I would also guess that if there are ANY mips users out
> > there that they would have to use some other ACCEPT_KEYWORDS value
> > because the shape of ~mips is so...bad.
> 
>  Don't remove an architecture.  Ask vapier what it means to reintroduce
> it.  Even if it rots, mark it as unmaintained and wait for someone to
> pick-up.

I question if this will hold true when gentoo-x86 goes git; at the 
very least folding an arch back into mainline should be a helluva lot 
easier.

Anyone got any comments on similar attempts?
~harring

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

[gentoo-dev] Re: Remove "dev"-status of mips profiles

[Torsten Veller]

* Torsten Veller <tove@gentoo.org>:
> Can we please move the mips profiles from "dev" to "exp" in
> profiles/profiles.desc?

Based on the current feedback I'll change it not earlier than friday
next week if nobody objects.

-- 
Thanks

Re: [gentoo-dev] Re: Remove "dev"-status of mips profiles

[Mark Loeser]

Torsten Veller <ml-en@veller.net> said:
> * Torsten Veller <tove@gentoo.org>:
> > Can we please move the mips profiles from "dev" to "exp" in
> > profiles/profiles.desc?
> 
> Based on the current feedback I'll change it not earlier than friday
> next week if nobody objects.

That would be nice.  I'd also love to know why we need about 150
different profiles for MIPS...

-- 
Mark Loeser
email         -   halcy0n AT gentoo DOT org
email         -   mark AT halcy0n DOT com
web           -   http://www.halcy0n.com

Re: [gentoo-dev] Re: Remove "dev"-status of mips profiles

[Samuli Suominen]

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

On 02/25/2010 05:14 PM, Mark Loeser wrote:
> Torsten Veller <ml-en@veller.net> said:
>> * Torsten Veller <tove@gentoo.org>:
>>> Can we please move the mips profiles from "dev" to "exp" in
>>> profiles/profiles.desc?
>>
>> Based on the current feedback I'll change it not earlier than friday
>> next week if nobody objects.
> 
> That would be nice.  I'd also love to know why we need about 150
> different profiles for MIPS...
> 

Every machine type profile has a developer, desktop and server sub profile.

How about deleting those? If you are capable of setting up a Gentoo/MIPS
setup, then you are certainly capable of setting up few profile defaults
on your own too.

See attached patch

[-- Attachment #2: profiles.desc.patch --]
[-- Type: text/plain, Size: 13247 bytes --]

--- profiles.desc.orig	2010-02-25 17:19:46.000000000 +0200
+++ profiles.desc	2010-02-25 17:21:34.000000000 +0200
@@ -44,158 +44,41 @@
 m68k            default/linux/m68k/10.0/server                  dev
 
 # MIPS Profiles
-mips            default/linux/mips/10.0/cobalt/desktop                          dev
-mips            default/linux/mips/10.0/cobalt/developer                        dev
-mips            default/linux/mips/10.0/cobalt/n32/desktop                      dev
-mips            default/linux/mips/10.0/cobalt/n32/developer                    dev
-mips            default/linux/mips/10.0/cobalt/n32/server                       dev
 mips            default/linux/mips/10.0/cobalt/n32                              dev
-mips            default/linux/mips/10.0/cobalt/n64/desktop                      dev
-mips            default/linux/mips/10.0/cobalt/n64/developer                    dev
-mips            default/linux/mips/10.0/cobalt/n64/server                       dev
 mips            default/linux/mips/10.0/cobalt/n64                              dev
-mips            default/linux/mips/10.0/cobalt/server                           dev
 mips            default/linux/mips/10.0/cobalt                                  dev
-mips            default/linux/mips/10.0/desktop                                 dev
-mips            default/linux/mips/10.0/developer                               dev
-mips            default/linux/mips/10.0/lemote/lm2e/desktop                     dev
-mips            default/linux/mips/10.0/lemote/lm2e/developer                   dev
-mips            default/linux/mips/10.0/lemote/lm2e/fulong/desktop              dev
-mips            default/linux/mips/10.0/lemote/lm2e/fulong/developer            dev
-mips            default/linux/mips/10.0/lemote/lm2e/fulong/n32/desktop          dev
-mips            default/linux/mips/10.0/lemote/lm2e/fulong/n32/developer        dev
-mips            default/linux/mips/10.0/lemote/lm2e/fulong/n32/server           dev
 mips            default/linux/mips/10.0/lemote/lm2e/fulong/n32                  dev
-mips            default/linux/mips/10.0/lemote/lm2e/fulong/n64/desktop          dev
-mips            default/linux/mips/10.0/lemote/lm2e/fulong/n64/developer        dev
-mips            default/linux/mips/10.0/lemote/lm2e/fulong/n64/server           dev
 mips            default/linux/mips/10.0/lemote/lm2e/fulong/n64                  dev
-mips            default/linux/mips/10.0/lemote/lm2e/fulong/server               dev
 mips            default/linux/mips/10.0/lemote/lm2e/fulong                      dev
-mips            default/linux/mips/10.0/lemote/lm2e/n32/desktop                 dev
-mips            default/linux/mips/10.0/lemote/lm2e/n32/developer               dev
-mips            default/linux/mips/10.0/lemote/lm2e/n32/server                  dev
 mips            default/linux/mips/10.0/lemote/lm2e/n32                         dev
-mips            default/linux/mips/10.0/lemote/lm2e/n64/desktop                 dev
-mips            default/linux/mips/10.0/lemote/lm2e/n64/developer               dev
-mips            default/linux/mips/10.0/lemote/lm2e/n64/server                  dev
 mips            default/linux/mips/10.0/lemote/lm2e/n64                         dev
-mips            default/linux/mips/10.0/lemote/lm2e/server                      dev
-mips            default/linux/mips/10.0/lemote/lm2f/desktop                     dev
-mips            default/linux/mips/10.0/lemote/lm2f/developer                   dev
-mips            default/linux/mips/10.0/lemote/lm2f/n32/desktop                 dev
-mips            default/linux/mips/10.0/lemote/lm2f/n32/developer               dev
-mips            default/linux/mips/10.0/lemote/lm2f/n32/server                  dev
 mips            default/linux/mips/10.0/lemote/lm2f/n32                         dev
-mips            default/linux/mips/10.0/lemote/lm2f/n64/desktop                 dev
-mips            default/linux/mips/10.0/lemote/lm2f/n64/developer               dev
-mips            default/linux/mips/10.0/lemote/lm2f/n64/server                  dev
 mips            default/linux/mips/10.0/lemote/lm2f/n64                         dev
-mips            default/linux/mips/10.0/lemote/lm2f/server                      dev
-mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/desktop            dev
-mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/developer          dev
-mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/n32/desktop        dev
-mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/n32/developer      dev
-mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/n32/server         dev
 mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/n32                dev
-mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/n64/desktop        dev
-mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/n64/developer      dev
-mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/n64/server         dev
 mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/n64                dev
-mips            default/linux/mips/10.0/lemote/lm2f/yeeloong/server             dev
 mips            default/linux/mips/10.0/lemote/lm2f/yeeloong                    dev
-mips            default/linux/mips/10.0/mipsel/desktop                          dev
-mips            default/linux/mips/10.0/mipsel/developer                        dev
-mips            default/linux/mips/10.0/mipsel/n32/desktop                      dev
-mips            default/linux/mips/10.0/mipsel/n32/developer                    dev
-mips            default/linux/mips/10.0/mipsel/n32/server                       dev
 mips            default/linux/mips/10.0/mipsel/n32                              dev
-mips            default/linux/mips/10.0/mipsel/n64/desktop                      dev
-mips            default/linux/mips/10.0/mipsel/n64/developer                    dev
-mips            default/linux/mips/10.0/mipsel/n64/server                       dev
 mips            default/linux/mips/10.0/mipsel/n64                              dev
-mips            default/linux/mips/10.0/mipsel/server                           dev
 mips            default/linux/mips/10.0/mipsel                                  dev
-mips            default/linux/mips/10.0/n32/desktop                             dev
-mips            default/linux/mips/10.0/n32/developer                           dev
-mips            default/linux/mips/10.0/n32/server                              dev
 mips            default/linux/mips/10.0/n32                                     dev
-mips            default/linux/mips/10.0/n64/desktop                             dev
-mips            default/linux/mips/10.0/n64/developer                           dev
-mips            default/linux/mips/10.0/n64/server                              dev
 mips            default/linux/mips/10.0/n64                                     dev
-mips            default/linux/mips/10.0/server                                  dev
-mips            default/linux/mips/10.0/sgi/ip22/desktop                        dev
-mips            default/linux/mips/10.0/sgi/ip22/developer                      dev
-mips            default/linux/mips/10.0/sgi/ip22/n32/desktop                    dev
-mips            default/linux/mips/10.0/sgi/ip22/n32/developer                  dev
-mips            default/linux/mips/10.0/sgi/ip22/n32/server                     dev
 mips            default/linux/mips/10.0/sgi/ip22/n32                            dev
-mips            default/linux/mips/10.0/sgi/ip22/n64/desktop                    dev
-mips            default/linux/mips/10.0/sgi/ip22/n64/developer                  dev
-mips            default/linux/mips/10.0/sgi/ip22/n64/server                     dev
 mips            default/linux/mips/10.0/sgi/ip22/n64                            dev
-mips            default/linux/mips/10.0/sgi/ip22/server                         dev
 mips            default/linux/mips/10.0/sgi/ip22                                dev
-mips            default/linux/mips/10.0/sgi/ip27/desktop                        dev
-mips            default/linux/mips/10.0/sgi/ip27/developer                      dev
-mips            default/linux/mips/10.0/sgi/ip27/n32/desktop                    dev
-mips            default/linux/mips/10.0/sgi/ip27/n32/developer                  dev
-mips            default/linux/mips/10.0/sgi/ip27/n32/server                     dev
 mips            default/linux/mips/10.0/sgi/ip27/n32                            dev
-mips            default/linux/mips/10.0/sgi/ip27/n64/desktop                    dev
-mips            default/linux/mips/10.0/sgi/ip27/n64/developer                  dev
-mips            default/linux/mips/10.0/sgi/ip27/n64/server                     dev
 mips            default/linux/mips/10.0/sgi/ip27/n64                            dev
-mips            default/linux/mips/10.0/sgi/ip27/server                         dev
 mips            default/linux/mips/10.0/sgi/ip27                                dev
-mips            default/linux/mips/10.0/sgi/ip28/desktop                        dev
-mips            default/linux/mips/10.0/sgi/ip28/developer                      dev
-mips            default/linux/mips/10.0/sgi/ip28/n32/desktop                    dev
-mips            default/linux/mips/10.0/sgi/ip28/n32/developer                  dev
-mips            default/linux/mips/10.0/sgi/ip28/n32/server                     dev
 mips            default/linux/mips/10.0/sgi/ip28/n32                            dev
-mips            default/linux/mips/10.0/sgi/ip28/n64/desktop                    dev
-mips            default/linux/mips/10.0/sgi/ip28/n64/developer                  dev
-mips            default/linux/mips/10.0/sgi/ip28/n64/server                     dev
 mips            default/linux/mips/10.0/sgi/ip28/n64                            dev
-mips            default/linux/mips/10.0/sgi/ip28/server                         dev
 mips            default/linux/mips/10.0/sgi/ip28                                dev
-mips            default/linux/mips/10.0/sgi/ip30/desktop                        dev
-mips            default/linux/mips/10.0/sgi/ip30/developer                      dev
-mips            default/linux/mips/10.0/sgi/ip30/n32/desktop                    dev
-mips            default/linux/mips/10.0/sgi/ip30/n32/developer                  dev
-mips            default/linux/mips/10.0/sgi/ip30/n32/server                     dev
 mips            default/linux/mips/10.0/sgi/ip30/n32                            dev
-mips            default/linux/mips/10.0/sgi/ip30/n64/desktop                    dev
-mips            default/linux/mips/10.0/sgi/ip30/n64/developer                  dev
-mips            default/linux/mips/10.0/sgi/ip30/n64/server                     dev
 mips            default/linux/mips/10.0/sgi/ip30/n64                            dev
-mips            default/linux/mips/10.0/sgi/ip30/server                         dev
 mips            default/linux/mips/10.0/sgi/ip30                                dev
-mips            default/linux/mips/10.0/sgi/ip32/desktop                        dev
-mips            default/linux/mips/10.0/sgi/ip32/developer                      dev
-mips            default/linux/mips/10.0/sgi/ip32/n32/desktop                    dev
-mips            default/linux/mips/10.0/sgi/ip32/n32/developer                  dev
-mips            default/linux/mips/10.0/sgi/ip32/n32/server                     dev
 mips            default/linux/mips/10.0/sgi/ip32/n32                            dev
-mips            default/linux/mips/10.0/sgi/ip32/n64/desktop                    dev
-mips            default/linux/mips/10.0/sgi/ip32/n64/developer                  dev
-mips            default/linux/mips/10.0/sgi/ip32/n64/server                     dev
 mips            default/linux/mips/10.0/sgi/ip32/n64                            dev
-mips            default/linux/mips/10.0/sgi/ip32/r10k/desktop                   dev
-mips            default/linux/mips/10.0/sgi/ip32/r10k/developer                 dev
-mips            default/linux/mips/10.0/sgi/ip32/r10k/n32/desktop               dev
-mips            default/linux/mips/10.0/sgi/ip32/r10k/n32/developer             dev
-mips            default/linux/mips/10.0/sgi/ip32/r10k/n32/server                dev
 mips            default/linux/mips/10.0/sgi/ip32/r10k/n32                       dev
-mips            default/linux/mips/10.0/sgi/ip32/r10k/n64/desktop               dev
-mips            default/linux/mips/10.0/sgi/ip32/r10k/n64/developer             dev
-mips            default/linux/mips/10.0/sgi/ip32/r10k/n64/server                dev
 mips            default/linux/mips/10.0/sgi/ip32/r10k/n64                       dev
-mips            default/linux/mips/10.0/sgi/ip32/r10k/server                    dev
 mips            default/linux/mips/10.0/sgi/ip32/r10k                           dev
-mips            default/linux/mips/10.0/sgi/ip32/server                         dev
 mips            default/linux/mips/10.0/sgi/ip32                                dev
 
 # PPC32 Profiles

Re: [gentoo-dev] Re: Remove "dev"-status of mips profiles

[Robin H. Johnson]

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

On Thu, Feb 25, 2010 at 05:24:25PM +0200, Samuli Suominen wrote:
> Every machine type profile has a developer, desktop and server sub profile.
> 
> How about deleting those? If you are capable of setting up a Gentoo/MIPS
> setup, then you are certainly capable of setting up few profile defaults
> on your own too.
Or better yet, you can stack your own mix of profiles:
# rm /etc/make.profile
# mkdir /etc/make.profile
# cat >/etc/make.profile/parent <<EOF
/usr/portage/profiles/default/linux/mips/10.0/cobalt/n32
/usr/portage/profiles/targets/developer
EOF

This avoids the need for desktop/developer/server everywhere, as I'm not
aware of ANY end profile of those that applies any other changes.

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

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

[gentoo-dev] Re: Remove "dev"-status of mips profiles

[Ryan Hill]

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

On Thu, 25 Feb 2010 11:30:32 +0100
Torsten Veller <ml-en@veller.net> wrote:

> * Torsten Veller <tove@gentoo.org>:
> > Can we please move the mips profiles from "dev" to "exp" in
> > profiles/profiles.desc?
> 
> Based on the current feedback I'll change it not earlier than friday
> next week if nobody objects.

Did you get feedback from anyone on mips@?


-- 
fonts,                                            by design, by neglect
gcc-porting,                              for a fact or just for effect
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

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

[gentoo-dev] Re: Remove "dev"-status of mips profiles

[Torsten Veller]

* Ryan Hill <dirtyepic@gentoo.org>:
> Torsten Veller <ml-en@veller.net> wrote:
> > * Torsten Veller <tove@gentoo.org>:
> > > Can we please move the mips profiles from "dev" to "exp" in
> > > profiles/profiles.desc?
> > 
> > Based on the current feedback I'll change it not earlier than friday
> > next week if nobody objects.
> 
> Did you get feedback from anyone on mips@?

No, I don't think so. Nonetheless mips was CC'ed on the last mail.

I also got no reply to the keywording bugs waiting for mips.
-- 
Thanks