Johannes Schauer: > Hi, > > On Thu, 10 Nov 2016 05:54:13 -0200 Johannes Schauer <jo...@debian.org> wrote: >> On Tue, 02 Aug 2016 22:49:00 +0200 Johannes Schauer <jo...@debian.org> wrote: >>> But then on IRC, HW42 suggested to approach this problem differently. >>> Instead of integrating the functionality of figuring out the right >>> repositories to reproduce the contents of a buildinfo file into sbuild, >>> write a tool that can drive any package builder (like pbuilder). > > there seems to be a conceptual problem with such an approach. > > For binNMUs, the full changelog entry has to be passed to sbuild or pbuilder. > How does one best pass such a multi-line value via command line options? Would > the best way to pass the changelog entry via the .buildinfo file? And if > pbuilder and sbuild then already are parsing the .buildinfo file, would it not > be better for the debrebuild machinery to be implemented by either in the > first > place?
Since this is somewhat relevant to the discussion in the other part of this thread: I don't think this is a conceptual problem. Sure it could be nicer if we don't had binNMUs, but I see no real problem in passing it via cmd line option or via a plain file. I would anyway modify debrebuild to be able to call sbuild/pbuiler/etc. directly and then you are able to use a tempfile cleanly.
signature.asc
Description: OpenPGP digital signature