[continued from previous message]
When I first ran into the problem of dpkg-source taking ages to build,
I thought of throwing together a script that just does the specific
tar(1) command to generate the .debian.tar.xz file, and a simple
template to generate the .dsc. But I knew that was a half-arsed
solution, so I prepared this patch.
Subjectively, I don't like that the patch couches this modality as
"don't generate an automatic diff" rather than a more straightforward
"just generate the debian/dsc files against existing orig tarball(s)
without doing any checks," but the former seemed like it was necessary
to fit into the man page conceptually. If you disagree, I'm happy to
rename the option and rewrite the doc text; just let me know what
approach I should take.
For the patch itself, I'm not very fond of the semantics it
introduces, because while something similar can probably be specified
for format 1.0, that one has rather loose semantics and is more prone
to error. Personally I don't trust myself to remember if I've done
changes to a tree (if it's not tracked by a VCS), so I see this
diluting its robustness and checks.
Depending on the scenarios you have in mind, a better option might
perhaps be to either make dpkg-source integrate more tightly with a
VCS, or perhaps create a new source format. Both of which I've had
in mind for a while, but see the motivation bit above.
I can't comment on this nor the rest, and I hope it's now clear why :]
I'm sorry for putting you though this whole thought process unnecessarily---
I can only hope the time you spent on it will bear fruit in other areas
of dpkg's development.
--Daniel
--
Daniel Richard G. ||
skunk@iSKUNK.ORG
My ASCII-art .sig got a bad case of Times New Roman.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)