[arch-dev-public] dependency rebuilds

[Dan McGee]

On Jan 4, 2008 1:36 PM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
>
> On Jan 4, 2008 9:18 AM, Paul Mattal <paul at mattal.com> wrote:
> > Aaron Griffin wrote:
> > > On Dec 30, 2007 11:37 PM, Paul Mattal <paul at mattal.com> wrote:
> > >> 1) the package y maintainer(s) notices package x in testing and rebuilds
> > >> package y
> > >>
> > >> 2) the package x maintainer(s) is responsible to find all packages y and
> > >> rebuilds all such packages y against the new package x
> > >
> > > There's a middle-ground here which I like, myself.
> > > 1.5)  the package x maintainer(s) is responsible to find all packages
> > > y and posts a todo list on the dashboard
> > >
> > > I like this method, but at the same time, it requires one to
> > > constantly scan the todo lists to see if a package of yours is there.
> >
> > A slight variation on this is to the todo list + what Damir did..
> > post to a todo list and *also* put a post on the arch-dev-public
> > list. This way people get push notification, and also a place to
> > track what they've done and what they haven't.
>
> I like this one.
>
> So ok, let me propose this:
> With rebuilds, it's the library maintainer's job to find all dep packages.
> There are then two choices:
>    * build everything yourself, if you feel like it (yay!)
>    * make a todolist and post on the arch-dev-public ML so we know
> that there is a new rebuild todolist.
>
> Sound like a good process?

+1. And if you are unsure about a package rebuild, push it to testing
and ask for a signoff from the maintainer (or anyone else).

-Dan