Broken upgrade paths in F7

Josh Boyer jwboyer at jdub.homelinux.org
Fri May 18 14:35:19 UTC 2007


On Fri, 2007-05-18 at 16:32 +0200, Dominik 'Rathann' Mierzejewski wrote:
> On Friday, 18 May 2007 at 16:20, Matthias Clasen wrote:
> > On Fri, 2007-05-18 at 16:13 +0200, Dominik 'Rathann' Mierzejewski wrote:
> > 
> > > > The reason it isn't made default is that there is no converse of it, 
> > > > IE --wait.  So by making it not default it gives users the opportunity to 
> > > > either use it if they like, or add a --nowait flag to disable it.  One can't 
> > > > have it disabled by default and force a way to have it actually wait.
> > > 
> > > Well, that's a regression compared to plague. Please fix it (or do I have
> > > to file a bug against koji to have it done?). I agree with Ralf that koji
> > > should mimic plague behaviour in that respect.
> > 
> > I'm sure there are a lot of people who would respond with saying that koji should 
> > mimic brew behaviour instead, i.e. stay as it is now. To make all the
> > picky developers happy, we probably need a full set of --wait/--nowait
> > options plus a config file to set the default. The build system is open
> > source now, so everybody can write patches...
> 
> I'm pretty sure there are more Extras contributors than Core. The system
> may be open-source, but not everyone speaks Python and the system has been
> forced upon us "packaging monkeys" (as some people like to call us).
> Could it at least NOT introduce radical changes in workflow, please?

You're confusing two issues.  Koji is simply a build server.  It doesn't
change workflow (other than perhaps some output and notification options
that likely need fixing).

What changes workflow is the release policies.

josh




More information about the Fedora-maintainers mailing list