Package: dgit Version: 4.2 On Mon, Jan 08 2018, Ian Jackson wrote:
> dgit build-source is a useful tool for getting a .dsc you can feed to > sbuild or lintian or other tools that don't understand git. (I was > using it that way myself yesterday.) > > One often wants to do that with a dirty tree. It would be useful to > be able to do it for refs other than head. (I think this is true of > push-source too.) > > But maybe that should be "build-dsc" or "export-dsc" or something? > After all for these purposes one doesn't need a .changes. Filing this as a separate bug; summary: Now that dgit has 'push-source', 'build-source' is not needed for uploads. However, we still want a subcommand that produces a source package that exactly matches HEAD/some user-provided ref, because we might want to feed this source package to a non-git tool like sbuild or lintian. 'build-source' can fulfill this need, but - it also produces a _source.changes, which is superfluous and might be confusing - it can be used only on HEAD - it requires the working tree to be clean - its name is less than ideal---producing a source package isn't to build something, in the sense that producing .debs is to build something So we should replace 'build-source' with 'export-dsc', which - produces a .dsc but no .changes - can be used on arbitrary refs (internally, invoke dpkg-source on a private git worktree) - does not require the working tree to be clean (probably should warn if tree is not clean, but should probably not require passing --allow-dirty in order to be used on a dirty working tree, because the .dsc is not for upload -- see discussion in #886625) -- Sean Whitton
signature.asc
Description: PGP signature
