[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Renaming a source package



Hi,

this is already in discussion within a bug (#744280); however I think it
is good to have the discussion a bit more general.

I have a source package (cpl-plugin-xsh) that creates three binary
packages:

cpl-plugin-xsh (the arch dependent binary)
cpl-plugin-xsh-doc (the arch independent documentation and manpages)
cpl-plugin-xsh-calib (an empty package that fetches some files from upstream)

Now, upstream changed the name of the package source to "xshoo", and for
consistency, I want to apply this change to the Debian packages.

Therefore I have now a source package cpl-plugin-xshoo, which creates
accordingly three binary packages with the same descriptions as above:

cpl-plugin-xshoo
cpl-plugin-xshoo-doc
cpl-plugin-xshoo-calib

Except this, nothing changed. The API of the package is identical to the
one before.

The files contained in cpl-plugin-(xsh|xshoo) and the files fetched by
cpl-plugin-(xsh|xshoo)-calib are versioned and therefore do not
conflict. The documentation packages contain manpages that actually do
conflict.

Question is now how to proceed:

* how do I declare that the *source* package cpl-plugin-xshoo is just
  renamed from cpl-plugin-csh?

* ho do I create a good transition?

I thought of two ways:

1. Just create a new source package cpl-plugin-xshoo that creates the
new cpl-plugin-xshoo* packages; set "Provides" and "Replaces" fields for
all three binary packages, and a "Breaks" field for the -doc (because of
the manpages). When they entered testing, manually remove all old
cpl-plugin-xsh* source and binary packages

2. From the new source, create a soource package that is still named
"cpl-plugin-xsh" that contains the new binary packages, and the old ones
as transitional dependencies (cpl-plugin-xsh has a Depends:
cpl-plugin-xshoo etc.) Once this entered testing, create a new source
package cpl-plugin-xshoo that contains the cpl-plugin-xshoo
packages. However, how do I declare then that the new source package just
overtakes the old source package?

I couldn't find anything about how to rename a *source* package in the
refguide; maybe it would be a good idea to have something there?

Best regards

Ole


Reply to: