[arch-dev-public] Todos for language specific rebuilds
anatol.pomozov at gmail.com
Sat Jan 11 17:04:37 UTC 2020
On Sat, Jan 11, 2020 at 6:58 AM Dave Reisner <d at falconindy.com> wrote:
> On Fri, Jan 10, 2020, 16:43 Christian Rebischke via arch-dev-public <
> arch-dev-public at archlinux.org> wrote:
> > Hi everybody,
> > I would like to propose that we create todos for rebuilds of language
> > specific packages.
> > We had two major rebuilds in the last months: python3.8 and ruby2.7.
> > Can we agree that we create a todo before such rebuilds?
> > The advantages outweigh the disadvantages. We would gain:
> I'm not sure I understand. Can you clearly state the problems we've
> encountered due to not doing this? What downsides do you see to your
> proposal? Can you think of any alternative solutions?
> * More people help rebuilding the packages.
> Solving the wrong problem, IMO. This is largely toil and should be
> automated away.
I agree with every statement that Dave made. Especially with this one.
We need to automate as much our daily routine as possible. Scripting/automation
is the only way to keep the increasing complexity of the system under control.
Adding more bureaucracy and putting more dumb manual work to the developers
will certainly slow down the development process.
> Foutrelis already has such a system that we've used for
> rebuilds in the past. We could/should instead work towards making this more
> generally available on the build machines.
I am a huge fan of this approach. I would really love to see the Foutrelis'
rebuild machine available as a tool at my workstation.
> * Every maintainer gets informed about the rebuild.
> As a maintainer, I don't care that you're rebuilding my package to keep up
> with library changes. Rather, I'm thankful to whomever did this for me.
> Why would a language rebuild differ from any other soname bump?
> * Maintainers have the possibility to test the packages.
Did you have any problems with testing the recent language rebuilds?
Could you please add more information how a todo list will fix it?
More information about the arch-dev-public