On Mon, 2007-07-16 at 00:28 +0200, Stefano Zacchiroli wrote:
> I don't want to see a bzr-foo package in the archive for each .py module > available on the internet which provides yet another sub-command for > bzr. I asked under the (wrong) assumption that bzrtools was a Debian > package shipping in a single Debian package several bzr addons. Under > that assumption it seemed reasonable to avoid creating a new package, > bug including your new addons as part of it. > > Since my assumption was wrong: what about creating a "bzr-addons" Debian > package containing the most used bzr addons out there instead of filing > an ITP for just one? I'd like to do the following: * rename the 'bazaar' package to 'baz' - both source and binary, though binary is the key one. This is because it is no longer the recommended tool from the 'Bazaar VCS Project' rather it is deprecated. Its useful for conversions to bzr though, so keeping it as 'baz' is good. * Create a 'bazaar' package which is a metapackage depending on bzr, recommending key plugins, and suggesting others. -Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
signature.asc
Description: This is a digitally signed message part
