Bzr plugins *must* die!

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Forest Bond wrote:
> Hi,

...

>> Basically, dapper uses python-central for managing python packages, and edgy+
>> uses python-support. I don't know where that corresponds in terms of debian
>> releases.
> 
> My Google skills are as good as they've always been.  Perhaps my reading skills
> are suffering.
> 
> I thought (and don't see any reason to think differently after having scanned
> the links you posted) that both python-central and python-support were being
> used due to lack of consensus as to which was preferable?  Am I misunderstanding
> things?
> 
> Thanks,
> Forest

I have no idea what the general consensus is. I'm not a DD, just a bzr release
manager who has been asked to produce some sort of .deb file at the same time
I create a tarball.

My knowledge is limited to:

1) We use a different setup to package for dapper
2) feisty, gutsy, hardy, intrepid, and debian unstable & experimental all use
the same 'control' file. (Which seems to list dependencies and necessary tools
to package the code.)
3) bzr-svn doesn't have a dapper package, but has a package for the rest
(though I've stopped making feisty ones, as that is now end-of-serviced.)
4) (1) uses python-support, (2) uses python-central. (Note this is the
opposite of what I've been saying, I just double checked the control file and
saw I was wrong. -central seems to be the "new" one.)

I would welcome someone like Jelmer, Robert, James Westby, etc to step up and
give the actual situation.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI2qCBJdeBCYSNAAMRAvYUAKCdaigr09Xjl92/VPY+MG3v4GB5WgCgveb5
dTOiLBfzcsPGA1tM7P38ZCY=
=g+8r
-----END PGP SIGNATURE-----