Control: tags -1 + moreinfo
Ian Jackson writes ("Re: extracting upstream source."):
> dgit often has "something like" the upstream source tree as a git
> tree object. dgit should provide a way for you to get at it.
Nowadays there is dgit import-dsc which goes a fair way towards this.
It is not entirely trivial to create a git tree object which is
exactly equivalent to the .orig, but, if one does dgit import-dsc
and specifies + on the destination branch, I think one of the
following things will result, depending on the source format:
* `3.0 (quilt)': Looking backward through the git history:
- A series of patches, being the debian/patches.
These are not annotated in any special way
- A merge commit which combines all the .origs and
the .debian.tar.*. If you just wanted the .origs, you
could delete /debian from the tree.
Annotated "[dgit import unpatched P V-R]"
- Origin commits, one per tarball
Annotated "[dgit import tarball P V[-R] FILENAME]"
* 1.0 native: a single origin commit, being the tarball,
annotated "[dgit import package P V-R]"
* 1.0 with diff:
- a single linear commit representing the
diff, annotated "[dgit import package P V-R]"
- The orig import, a "[dgit import orig ...]" as above.
I hope this is of some use. I appreciate that it's a bit late to be
replying to this now. Anyway, the above is not 100% convenient but
ISTM that it is good enough given the problem, so I propose to close
this bug unless someone thinks it would be worth the effort dgit
providng something more "cooked".
Thanks,
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> 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.
