Hi Bastien, On Wed, Jun 29, 2011 at 06:12:09PM +0200, Bastien ROUCARIES wrote: > Package: gitpkg > Version: 0.19 > Severity: wishlist > > Please add some example to man pages, particularly concerning pristine tar > workflow.
Do you have some particular examples of things that aren't clear in mind? The basic idea of gitpkg is to _not_ tie you into any particular workflow, ie. you just use the standard git tools however works best for a particular project, and so long as you can identify a treeish that corresponds to the debianised source you want to export (and one for the orig source if you need to export that also), then gitpkg can make you a source package of it, regardless of what workflow you used to create that repo, or even if you changed workflows somewhere along the line ... This means you can use it with upstream repos, or other people's repos, without requiring them to know anything at all about gitpkg in advance. If you enable the pristine-tar-pre-export-hook (as described in the man page), then when you nominate the treeish for your debian revision, the correct pristine tarball will be exported as the orig. To create the pristine tar commits in the repo, you likewise just use pristine tar as per its own instructions. I'm happy to clarify anything in the docs that isn't clear about that, but you'll have to help me out and point a bit more explicitly, since it's already fairly verbose, and I thought it did already cover most or all of this? (of course I'm the wrong person to judge that, as I already know too much about how it works, so suggestions are welcome.) Cheers, Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
