Sean Whitton writes ("Bug#1079762: dgit: Supporting generated files
(`debian/control` and `debian/tests/control`) not commited to git"):
> Is that the sort of committing-of-generated-artifacts you object to? Or
> is it okay if the maintainer never sees it?
For comparison, some of the best workflows for generating "3.0
(quilt)" .dscs also commit output files, namely debian/patches.
In those workflows the primary representation of the patch queue is in
git commits, and the in-tree version is there for compatibility with
dpkg-source.
git-debrebase does this when used with "3.0 (quilt)". I believe that
some other tools like git-dpm and git-debcherry do too.
ISTM that debian/control could be thought of similarly.
One key question is: what happens if you start with transformed view,
the edit the package? Either the generated files or the inputs.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
