Sean Whitton writes ("Bug#886969: Problems with export-dsc and push-source on
arbitrary refs"):
> On Mon, Jun 25 2018, Ian Jackson wrote:
> > export-dsc has no push and that makes the whole split brain mode seem
> > rather odd.
>
> Hmm, why would it be odd simply to generate the dgit view, export it as
> a dsc and then discard it?
I think I am really just struggling slightly with what export-dsc
ought to do.
dgit's "source package" output (as provided by the "dgit push") is
actually a source-package-and-git-commit. The local source packages
with no Dgit header are an intermediate step, and ideally wouldn't be
distributed.
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.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
