[arch-dev-public] dependency rebuilds
tom at archlinux.org
Fri Jan 4 17:22:33 EST 2008
Paul Mattal wrote:
> Aaron Griffin 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
>>>>> 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
>> 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.
> Sounds good. Put the package list, with the following observations:
> * if you decide to build everything yourself, think about that first and
> want to take that responsibility; releasing is more than just
> rebuilding, and by rebuilding you potentially break something and
> thereby take on responsibility to fix it in relatively short order (even
> if it's just in testing)
> * generally make sure the emailed todo list actually contains the list
> of packages, or at minimum a direct link to the todo list; it gives
> people no excuse not to notice
I'm hesitant to suggest this, as I'm not able to actually make it
happen, but could the addition of a package to a to-do list trigger the
same automated-mail thing that is currently used for out-of-date flags?
That would make option two a single task: make a to-do list.
More information about the arch-dev-public