[Pkg-bazaar-maint] package versioning for multiple distro's

[Adeodato Simó]

* Robert Collins [Wed, 01 Aug 2007 11:36:47 +1000]:

> But one way to solve this I guess is to add a version for the distro,
> giving a partial ordering.

> e.g.
> dapper: UPSTREAM-DEBIAN-0
> edgy: UPSTREAM-DEBIAN-1
> feisty: UPSTREAM-DEBIAN-2

> Thoughts?

Another possibility which I think it's better is using the release name
in the version; I think it's better because it's clear from looking at
the package for which distro it's targetted. This can be convinient.

  Original: bzr_0.18-1
  
  Ubuntu backports:
            bzr_0.18-1~dapper1
            bzr_0.18-1~edgy1
            bzr_0.18-1~feisty1

This works nicely in Ubuntu because of the intentional incremental sort
of the release names. If you rather not depend on that, but still
include names in the version (which, as said, I really recommend):

            bzr_0.18-1~0dapper1
            bzr_0.18-1~1edgy1
            bzr_0.18-1~2feisty1

> gutsy: UPSTREAM-DEBIAN-3

This should be not needed. Gutsy names should be 0.18-X or 0.18-0ubuntuX,
no?

> and debian flavours
> sarge: UPSTREAM-DEBIAN-0
> etch: UPSTREAM-DEBIAN-1

Are you going to prepare these as well? etch is being handled at the
moment via backports.org, whose versioning policy is 0.18-1~bpo1. I
planned on doing the backports.org uploads, but these can only be done
after the package has migrated to testing. If you were planning on doing
these yourself, it'd be nice that you made your etch package suitable
for uploading to backports.org when the time comes (I can give you the
details, or you can leave up to me preparing the etch packages (for
bazaar-vcs.org; I'm not interested in sarge, though).

Cheers,

-- 
Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
 
And how do you tell an extroverted mathematician? He looks at *your* shoes
while he's talking to you.