bzr for packaging

Martin Pitt martin.pitt at ubuntu.com
Thu Mar 29 07:55:45 BST 2007


Hi,

Matt Zimmerman [2007-03-28 10:39 -0700]:
> > Once we will have a reliable bzr import of upstream versions/RCS, this
> > might be beneficial, but right now it would just waste bandwidth
> > without giving any visible benefits. For a new upstream release I just
> > rm everything but debian/ and unpack the new orig.tar.gz.
> 
> I don't think it provides more than trivial benefit for a package where only
> debian/ is in revision control.  It won't help to merge your changes,
> because they're stored as diffs.

If we can get https://wiki.ubuntu.com/NoMoreSourcePackages working,
and bzr loom becomes reality, then it would make a difference, I
think.

> > Yes. I wrote http://people.ubuntu.com/~pitti/scripts/bzrdc ages ago
> > ('bzr debian commit') and have used it so far. A few weeks ago I
> > actually discovered debcommit, but (1) that doesn't ask me for
> > confirmation and (2) old habits die hard :).
> 
> (1) is trivial to fix; why not add that to debcommit and create an alias to
> help you tackle (2)? :-)  Better to standardize on tools which are in the
> distribution so that everyone benefits from improvements.

I wouldn't like to change the default behaviour of debcommit, but I
agree that adding a --confirm option and 

  alias bzrdc='debcommit --confirm'

is the way to go. :)

Thanks,

Martin
-- 
Martin Pitt        http://www.piware.de
Ubuntu Developer   http://www.ubuntu.com
Debian Developer   http://www.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20070329/eca2fd72/attachment-0001.pgp 


More information about the ubuntu-devel mailing list