Package: devscripts Version: 2.18.3 X-debbugs-cc: ijack...@chiark.greenend.org.uk Control: affects -1 dgit
[affects dgit because git-deborig is mentioned in some dgit manpages] Dear maintainer, In recent dgit you can configure a build products dir (or "build area") where .changes, .dsc, .debian.tar.gz etc. will be put. In particular, if this is configured, dgit expects .orig.tar to be in the build products dir, and will fail if the .orig.tar is in .. and the configured build products dir is not the parent directory. git-deborig will only output .orig.tar files to the parent directory. So if you want to use git-deborig and dgit when you have a build products dir other than .. configured, you have to manually move the .orig.tar from .. into the build products dir before you can build. This is inconvenient. git-deborig was designed for dgit workflows, so this is something of a regression. One possibility is to have git-deborig read dgit's configuration. But dgit permits the user to configure a different build products dir for each distribution (e.g. Debian & Ubuntu), and if git-deborig wants to ask dgit which build products dir is appropriate for the current repo, dgit has to make a network connection to canonicalise the suite, which is slow and might be privacy-infringing. Ian and I talked about this and wonder if we should establish a `debian` git configuration namespace which could contain a key for the build products dir which would be respected by both dgit and git-deborig. We think that if this is done, the devscripts package should own the namespace. What do those working on devscripts think? -- Sean Whitton
signature.asc
Description: PGP signature
