Gentoo Archives: gentoo-dev

From: Thomas Kahle <tomka@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Ruby keywording
Date: Wed, 07 Mar 2012 15:01:30
In Reply to: Re: [gentoo-dev] Ruby keywording by Alexis Ballier
On 09:25 Wed 07 Mar 2012, Alexis Ballier wrote:
> On Wed, 07 Mar 2012 08:00:16 +0100 > ""PaweĊ‚ Hajdan, Jr."" <phajdan.jr@g.o> wrote: > > > Also the inter-bug dependencies are often not resolved correctly, > > > that is the to be keyworded package depends on non-keyworded stuff > > > not listed in the bug. > > > > And this is even worse. Please check things with repoman before filing > > bugs. You can even write automated scripts at least for the "check > > whether we got all deps right" part. > > As a maintainer I can tell you that when you drop keywords on B because > it needs non keyworded A, then drop keywords on C because it needs > latest B then drop keywords on D because it needs latest C, you have > completely forgotten that some arches need A, which ones, etc. There are > scripts for this, and I hope arch teams that like to have a list use > them.
What scripts are out there? I just do iterated repoman calls without much automation (pretty much as described below). Got anything better? -> please post it! Cheers, Thomas
> As occasionally doing fbsd keywording, I almost never read nor use a > list that is provided since the above scenario often occurs (or at > least used to). Instead of this, I do a depth-first keywording of > packages repoman tells are missing. The deepest package is in the > latest tab of my terminal emulator :) I'll run repoman anyway, > and this approach allows a double checking. Also, since this means I'll > start committing from the leaves of the depgraph, this ensures no > package has broken deps between commits (with the exception of circular > deps of course). > > A. >
-- Thomas Kahle


File name MIME type
signature.asc application/pgp-signature


Subject Author
Re: [gentoo-dev] Ruby keywording Alexis Ballier <aballier@g.o>