FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

 
 
LinkBack Thread Tools
 
Old 02-16-2011, 01:31 AM
Donnie Berkholz
 
Default RFC: package.keywords-compatible snippets when stabilizing multiple packages

On 09:10 Tue 15 Feb , Gilles Dartiguelongue wrote:
> Le lundi 14 fĂ©vrier 2011 Ă* 19:19 +0100, "PaweĹ‚ Hajdan, Jr." a Ă©crit :
> > On 2/14/11 9:13 PM, Samuli Suominen wrote:
> > > And http://bugs.gentoo.org/show_bug.cgi?id=349053#c1 ? I tried to
> > > provide a clue howto get usable p.keywords list easy.
> >
> > IMHO it's in the middle. I still have to do a manual step, but at least
> > it's pretty straightforward. Anyway, I think a list that can be blindly
> > copy-pasted makes things even easier.
> >
>
> I don't think making a list for each arch is going to make anything any
> easier for maintainers requesting stabilization, which means those list
> we need more time to generate before being released. You just move the
> problem to another place.

Why would you need to do that? Can't you just make a single list that
either has keywords for every arch or a ** ? Presumably every arch needs
a certain set of packages stable, and it doesn't matter if you
redundantly specify packages that are already stable.

--
Thanks,
Donnie

Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.com
 
Old 02-16-2011, 12:17 PM
Tobias Klausmann
 
Default RFC: package.keywords-compatible snippets when stabilizing multiple packages

Hi!

On Tue, 15 Feb 2011, Donnie Berkholz wrote:
> On 09:10 Tue 15 Feb, Gilles Dartiguelongue wrote:
> > Le lundi 14 fĂ©vrier 2011 Ă* 19:19 +0100, "PaweĹ‚ Hajdan, Jr." a Ă©crit :
> > > On 2/14/11 9:13 PM, Samuli Suominen wrote:
> > > > And http://bugs.gentoo.org/show_bug.cgi?id=349053#c1 ? I tried to
> > > > provide a clue howto get usable p.keywords list easy.
> > >
> > > IMHO it's in the middle. I still have to do a manual step, but at least
> > > it's pretty straightforward. Anyway, I think a list that can be blindly
> > > copy-pasted makes things even easier.
> >
> > I don't think making a list for each arch is going to make anything any
> > easier for maintainers requesting stabilization, which means those list
> > we need more time to generate before being released. You just move the
> > problem to another place.
>
> Why would you need to do that? Can't you just make a single list that
> either has keywords for every arch or a ** ? Presumably every arch needs
> a certain set of packages stable, and it doesn't matter if you
> redundantly specify packages that are already stable.

Yes it does. I for one just use the list, compile and test all
the packages. If an entry is already stable, that effort is
wasted.

I think automatically generating per-arch lists and dumping them
on the bug is a nice way to do it. Having a "tabled list" for use
by the maintainer and then generating one comment per
arch-specific list seems like a good idea to me. Yes it is more
verbose on the bug, but that is a little price to pay, I'd say.

Regards,
Tobias

--
printk(KERN_ERR "msp3400: chip reset failed, penguin on i2c bus?
");
linux-2.2.16/drivers/char/msp3400.c
 
Old 02-16-2011, 02:14 PM
Donnie Berkholz
 
Default RFC: package.keywords-compatible snippets when stabilizing multiple packages

On 14:17 Wed 16 Feb , Tobias Klausmann wrote:
> Hi!
>
> On Tue, 15 Feb 2011, Donnie Berkholz wrote:
> > On 09:10 Tue 15 Feb, Gilles Dartiguelongue wrote:
> > > Le lundi 14 fĂ©vrier 2011 Ă* 19:19 +0100, "PaweĹ‚ Hajdan, Jr." a Ă©crit :
> > > > On 2/14/11 9:13 PM, Samuli Suominen wrote:
> > > > > And http://bugs.gentoo.org/show_bug.cgi?id=349053#c1 ? I tried to
> > > > > provide a clue howto get usable p.keywords list easy.
> > > >
> > > > IMHO it's in the middle. I still have to do a manual step, but at least
> > > > it's pretty straightforward. Anyway, I think a list that can be blindly
> > > > copy-pasted makes things even easier.
> > >
> > > I don't think making a list for each arch is going to make anything any
> > > easier for maintainers requesting stabilization, which means those list
> > > we need more time to generate before being released. You just move the
> > > problem to another place.
> >
> > Why would you need to do that? Can't you just make a single list that
> > either has keywords for every arch or a ** ? Presumably every arch needs
> > a certain set of packages stable, and it doesn't matter if you
> > redundantly specify packages that are already stable.
>
> Yes it does. I for one just use the list, compile and test all
> the packages. If an entry is already stable, that effort is
> wasted.
>
> I think automatically generating per-arch lists and dumping them
> on the bug is a nice way to do it. Having a "tabled list" for use
> by the maintainer and then generating one comment per
> arch-specific list seems like a good idea to me. Yes it is more
> verbose on the bug, but that is a little price to pay, I'd say.

Is using autounmask an option instead? That generates a nice little file
with everything that was actually unmasked, assuming it's a single
dependency tree of packages.

--
Thanks,
Donnie

Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.com
 
Old 02-16-2011, 02:50 PM
Jeroen Roovers
 
Default RFC: package.keywords-compatible snippets when stabilizing multiple packages

On Wed, 16 Feb 2011 09:14:59 -0600
Donnie Berkholz <dberkholz@gentoo.org> wrote:

> On 14:17 Wed 16 Feb , Tobias Klausmann wrote:
> > I think automatically generating per-arch lists and dumping them
> > on the bug is a nice way to do it. Having a "tabled list" for use
> > by the maintainer and then generating one comment per
> > arch-specific list seems like a good idea to me. Yes it is more
> > verbose on the bug, but that is a little price to pay, I'd say.

+1

> Is using autounmask an option instead? That generates a nice little
> file with everything that was actually unmasked, assuming it's a
> single dependency tree of packages.

autounmask takes ages on slow systems.


jer
 
Old 02-16-2011, 04:21 PM
"Paweł Hajdan, Jr."
 
Default RFC: package.keywords-compatible snippets when stabilizing multiple packages

On 2/15/11 9:10 AM, Gilles Dartiguelongue wrote:
> I don't think making a list for each arch is going to make anything any
> easier for maintainers requesting stabilization, which means those list
> we need more time to generate before being released. You just move the
> problem to another place.

I was expecting such argument. It's a good point, but please consider
the following:

- if the stabilization list has been created automatically, we should
adjust the tool to print in a format more suitable for the intended
audience (arch developers)

- if the stabilization list has been created manually, what prevents you
from doing it in a slightly different way? I think it doesn't change the
amount of work, and might even decrease it (no need for pretty tables)
 
Old 02-16-2011, 05:23 PM
Matt Turner
 
Default RFC: package.keywords-compatible snippets when stabilizing multiple packages

On Tue, Feb 15, 2011 at 8:10 AM, Gilles Dartiguelongue <eva@gentoo.org> wrote:
> I don't think making a list for each arch is going to make anything any
> easier for maintainers requesting stabilization, which means those list
> we need more time to generate before being released. You just move the
> problem to another place.

From my perspective, it should be more about making it easier for arch
teams to test the packages.

Lots of talk about what to do about "slacking arches". Well, maybe
just give them an easy list they can grep to get the packages they
need to test would help.

Seems like a fairly straight forward thing to do. A tool to automate
this process for the maintainers might be nice.

Matt
 
Old 02-17-2011, 12:42 PM
Gilles Dartiguelongue
 
Default RFC: package.keywords-compatible snippets when stabilizing multiple packages

For gnome it's semi-automated but it's still a matter of hours of work
to adjust, not even talking about the fact that we miss some
dependencies sometimes which means we have to upload the list multiple
times. Uploading 9 lists each time there is a modification will not make
the work of anyone clearer in the end.

--
Gilles Dartiguelongue <eva@gentoo.org>
Gentoo
 

Thread Tools




All times are GMT. The time now is 09:03 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org