Den 20. feb. 2013 16:23, skreiv Thomas Goirand:
If that doesn't work, you can use the pristine-tar thing, that should
always work.
I never used it, probably I should learn, it seems quite convenient. Can
anyone
give feedback about it?
My workflow for anything outside of this team and not intended for
Ubuntu directly is with git and a full source branch. I don't package
often enough to remember everything from time to time, but it's no more
than a quick google search away. Roughly the workflow is to use uscan to
download the source tarball, git-import-orig with pristine tar to import
upstream code into upstream branch. git-import-orig handles committing
an tagging necessary changes. Using quilt I can then modyfi anything I
like in the source directories, and quilt will keep every change in the
debian/patches folder. If I accidentally touch anything not handled by
quilt this is easily reverted with a single-file checkout. When I'm
happy with the changes I build the package using git-buildpackage
(--git-ignore-new if I want to test before commit)
--git-builder=pdebuild. Once I'm ready to upload the debian release
commit is tagged. Because of pristine tar, the upstream release tarball
can be recreated from the upstream branch, and everybody should be happy.
IMHO patching and patch handling is way easier in git than in svn,
mostly because I never copy or export anything to create and test the
patches. I totally agree that all changes to the source should be kept
as patches.
Regards
Andreas Noteng
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/512506c1.8030...@noteng.no
