[maemo-developers] Autobuilder repository priority ?

From: Graham Cobb g+770 at cobb.uk.net
Date: Tue Nov 3 01:02:31 EET 2009
On Monday 02 November 2009 21:52:48 Jeremiah Foster wrote:
> On Nov 2, 2009, at 10:27, Ed Bartosh wrote:
> > 2009/11/2 Jeremiah Foster <jeremiah at jeremiahfoster.com>:
> >> On Nov 1, 2009, at 18:05, Ed Bartosh wrote:
> >>> Idea of having separate queue for Extras updates sounds more
> >>> promising
> >>> to me. Developers might become confused with all this set of
> >>> repositories, queues and processes, but the idea is good. I support
> >>> this.
> >
> > What about this? Can we have separate queue for updates? Any other
> > ideas?
> Can you explain how this might work and it's advantages? I am not
> against it aside from the fact that I think another repo is confusing.
> Is the proposal to create a repo called extras-updates which would
> hold only updates to software that has already existed in the repos? I
> don't see how that is different from just updating the existing
> package with new software. If you want to pull in different version
> numbers than what exists why would you need a separate repo?

Sorry, like Jeremiah I am now a bit confused.  Can you, Ed, please summarise 
what this proposal is?  You mention separate queue but which queue are you 
referring to?  Does the suggestion involve additional repositories? And/or 
does it involve differnet rules for which repositories will be in scope 
during a build?  Or what.

Sorry if everyone else understands this but I don't.

> I think this is adding complexity - and we are in danger of having too
> much complexity already.

Definitely a point worth bearing in mind!

More information about the maemo-developers mailing list