Packaging with git question
* Christophe Monniez <dfence.242 at gmail.com> [Fri Sep 17, 2010 at 06:37:32PM +0200]:
> On Fri, Sep 17, 2010 at 5:33 PM, Michael Prokop <mika at debian.org> wrote:
> > * Christophe Monniez <dfence.242 at gmail.com> [Thu Sep 16, 2010 at 10:15:11AM +0200]:
> >> I used git-buildpackage to update afflib to the new 3.6.2 version
> >> (even if I know that squeeze is frozen).
> >> I 'm prett happy with the result but as always, I'm affraib to break
> >> something in the work made
> >> by others (for instance, the latest afflib work was made by?Cristian Greco).
> >> I did not push my work yet. I made a tar.gz backup of the afflib.git
> >> directory on alioth.
> >> My questions are:
> >> - Do you think that I can push my work ?
> >> - Is there other extra safety precautions to do ?
> >> - Is there a best practice for that kind of co-working ?
> > Just work on an extra branch and push that extra branch instead of
> > pushing the master branch itself. This should provide what you'd
> > like to get, nor?
> Well, git-buildpackage automatically worked on the master, upstream
> and pristine-tar branch.
Just specify the according branches as options to git-buildpackage,
see options --git-upstream-branch, --git-debian-branch and
--git-ignore-branch.
I usually build with something like:
git-buildpackage --git-debian-branch="$(git branch | awk -F\*\ '/^* / { print $2}' )" ...
regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/forensics-devel/attachments/20100917/bb6ac38e/attachment.pgp>
Reply to: