[Pkg-bazaar-maint] To arch:any or not to arch:any

[Adeodato Simó]

Hello guys.

The next Bazaar release, 0.19, will be the first to include C extensions
via Pyrex, and the packaging will have to ship them somehow. I'd like to
receive input in a couple of issues:

  * I was planning on moving bzr from arch:all to arch:any. However this
    makes the package loose the nice property of the same package being
    (TTBOMK) installable without rebuilding it in any Debian/Ubuntu
    distribution supporing pycentral.

    But backports seem to be happening anyway despite the above, so it
    doesn't seem such a big loss after all, does it?

    Is there anybody who would strongly prefer keeping bzr as arch:all,
    thus shipping the extension module in a separate package (which bzr
    would Recommend). I'd rather not do that, but I'm open to hear
    rationales for it.

  * At the moment bzrlib is available under all installed Python
    versions, not only the default version: pycentral takes care of
    that. I doubt much people are using bzrlib with a non-default python
    version (let alone using bzrlib outside from bzr), but I'd still
    like to ship compiled extension for all available python versions.
    Anybody object to that?

That said, I'm volunteering to make the necessary packaging changes for
0.19~rc1.

Cheers,

-- 
Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
 
                                      Listening to: Fangoria - A tu lado