From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Identifying inherit-only / usable profiles (round 2)
Date: Sun, 3 Apr 2005 12:55:09 +0900 [thread overview]
Message-ID: <200504031255.09565.jstubbs@gentoo.org> (raw)
In-Reply-To: <1112460673.7137.1.camel@amd64.anyarch.net>
On Sunday 03 April 2005 01:51, Daniel Ostrow wrote:
> On Sat, 2005-04-02 at 11:41 -0500, Chris Gianelloni wrote:
> > On Sat, 2005-04-02 at 16:35 +0900, Jason Stubbs wrote:
> > > Seeing that I added that output, I guess I should reply. The reason for
> > > it was that only one profile per keyword will be checked at the moment.
> > > Essentially, the output was both to make people aware of this fact and
> > > to make sure people know *which* profile is being checked.
> > >
> > > I figure your going to tell me that all listed profiles should be
> > > checked and I'd have to agree so, if it'll prevent the addition of
> > > another useless file, I guess I'll get right on it.
> >
> > Give us a shout when you have something to test and I'll gladly fill up
> > profiles.desc with the valid profiles.
>
> I'm going to be making at least 2 dev profiles over the next week for
> ppc64, glad that will be able to be checked.
>
> Let us know when you need testers.
http://dev.gentoo.org/~jstubbs/repoman-2.0.51.19.patch
Changes:
* All profiles listed in profiles.desc are checked.
* Masked packages are not checked unless --include-masked is specified, when
- repoman is being called at category or tree level, and
- commit has not been specified.
* Removed several expensive but seemingly useless operation for a 90% speedup.
With regard to the useless operations, they were there to restore the trees
and config objects to initial state but I can't find anything that actually
modifies their states. I ran a couple of category checks with and without the
patch and didn't get any differing results, but keep your eyes open anyway.
Regards,
Jason Stubbs
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2005-04-03 3:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 22:23 [gentoo-dev] Identifying inherit-only / usable profiles (round 2) Aaron Walker
2005-03-01 10:21 ` Aaron Walker
2005-03-01 14:47 ` Chris Gianelloni
2005-03-01 15:07 ` Aaron Walker
2005-03-07 18:42 ` Chris Gianelloni
2005-03-08 14:24 ` Mike Frysinger
2005-03-09 4:56 ` Aaron Walker
2005-03-09 16:46 ` Chris Gianelloni
2005-03-09 23:57 ` Jason Stubbs
2005-03-10 0:49 ` Mike Frysinger
2005-03-10 0:50 ` Mike Frysinger
2005-03-10 1:41 ` Jerome Brown
2005-03-10 12:56 ` Aaron Walker
2005-03-10 15:49 ` Chris Gianelloni
2005-03-10 15:53 ` Ciaran McCreesh
2005-03-10 16:27 ` Chris Gianelloni
2005-03-13 18:17 ` Jerome Brown
2005-03-13 20:19 ` Chris Gianelloni
2005-03-13 22:05 ` Martin Schlemmer
2005-03-14 14:43 ` Mike Frysinger
2005-03-10 16:55 ` Lina Pezzella
2005-03-30 9:27 ` Aaron Walker
2005-03-30 14:00 ` Chris Gianelloni
2005-04-01 18:50 ` Aaron Walker
2005-04-01 19:31 ` Mike Frysinger
2005-04-01 19:46 ` Chris Gianelloni
2005-04-01 21:02 ` Mike Frysinger
2005-04-02 6:15 ` Aaron Walker
2005-04-02 7:35 ` Jason Stubbs
2005-04-02 16:41 ` Chris Gianelloni
2005-04-02 16:51 ` Daniel Ostrow
2005-04-03 3:55 ` Jason Stubbs [this message]
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=200504031255.09565.jstubbs@gentoo.org \
--to=jstubbs@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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