[Pkg-Cyrus-imapd-Debian-devel] RFC: Renaming the packages

[Sven Mueller]

Henrique de Moraes Holschuh wrote on 30/11/2005 15:43:
> We are approaching the upload to unstable, so it is time to question a few
> choices of the past, to see if we should not change them.

Fine.

> The first issue is the naming of the packages.  Keep in mind that if we
> change the naming convention, I will change the 2.1 packages accordingly,
> and that the 1.5 packages are gone.

Well, I have no strong feelings regarding the rename of the 2.2
packages. However I would not like to rename the 2.1 packages, since
that would (as Benjamin pointed out) make upgrades from sarge to etch
more difficult (either by requiring manual intervention or by using
transitional packages).

> The rationale for a possible renaming of the packages is that "cyrus##-*" is
> really awkward, and does NOT reflect the upstream name of the application at
> all.

The good thing however was that this kept the cyrus-imapd related
packages together in the package list. After the rename, the cyrus-sasl
packages will get mixed in. This is no big problem though.

> I propose we change the naming convention as follows:
[...]
>   cyrus-base-2.#  (rename of cyrus-common)
>   ...
>
> What do you guys think about the whole idea? and what about the cyrus-common
> to cyrus-base rename?

Why rename -common to -base? Most other packages I know of also use the
-common approach AFAIR.

cu,
sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 186 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-imapd-debian-devel/attachments/20051130/02b5e13c/signature.pgp