Hello, On Mon, Jun 25 2018, Ian Jackson wrote:
> So there is an argument that doing a source-package-ful "export" from > a git branch, using dgit, ought to generate both a .dsc and a dgit > view git branch, and write something about the result into the Dgit > header in the .dsc. That way `dgit import-dsc' would return the > original git branch. > > To make that work, dgit export-dsc would have to (i) take a git remote > and (ii) somehow be able to verify that the url was publicly > accessible (maybe like git-request-pull does). > > I can see that spitting out a "dumb" source package is useful in some > situations but anyone who receives it is necessarily disadvantaged > compared to someone who gets the hybrid .dsc + git branch format. When we first discussed this the intention was spitting out a dumb source package for feeding to things like sbuild. There was never any plan to produce something that `dgit import-dsc` can consume to reproduce the git branch. -- Sean Whitton
signature.asc
Description: PGP signature
