From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Remove "dev"-status of mips profiles
Date: Thu, 11 Feb 2010 21:21:08 +0200 [thread overview]
Message-ID: <4B7458A4.9040809@gentoo.org> (raw)
In-Reply-To: <b204a35ff90372b6a274de6d266e0cca@jolexa.net>
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
next prev parent reply other threads:[~2010-02-11 19:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 15:54 [gentoo-dev] Remove "dev"-status of mips profiles Torsten Veller
2010-02-11 16:06 ` [gentoo-dev] " Christian Faulhammer
2010-02-11 18:41 ` [gentoo-dev] " Brian Harring
2010-02-11 18:56 ` Jeremy Olexa
2010-02-11 19:08 ` Brian Harring
2010-02-11 19:16 ` Brian Harring
2010-02-11 19:21 ` Samuli Suominen [this message]
2010-02-11 21:12 ` [gentoo-dev] " Christian Faulhammer
2010-02-11 21:22 ` Brian Harring
2010-02-25 10:30 ` Torsten Veller
2010-02-25 15:14 ` Mark Loeser
2010-02-25 15:24 ` Samuli Suominen
2010-02-25 19:29 ` Robin H. Johnson
2010-02-25 23:57 ` Ryan Hill
2010-02-26 6:57 ` Torsten Veller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B7458A4.9040809@gentoo.org \
--to=ssuominen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox