[Pkg-mono-devel] Debian CLI Policy 0.5.1 available

[Mirco Bauer]

On Sun, 2008-06-15 at 19:12 +0200, David Paleino wrote:
> I see that the example "source names" (§2.6) are:
> 
> * (debian) source package names:
>       gtk-sharp2
>       log4net
>       libflickrnet
> 
> A package I'm working on, i.e. libanculus-sharp (the next upload will rename it
> to libanculus0.3.1-cil), has "libanculus-sharp" as package name, while a
> Policy-compliant one would be "libanculus" or "anculus-sharp". What to do now?
> I believe that changing the source name, the package would go through NEW --
> but I'd like to avoid it.

first, that list was just an example of source package names. The exact
source package name does not really matter, as it doesn't affect the
binary packages and thus not the usability of the software on a debian
system.

So stick to the name that upstream uses for their tarball name, thats
usually the source package name in debian (but don't have to).

Regarding NEW queue, rename a binary package and/or source package will
make it go through the NEW queue again. But it's usually faster for
packages that do a rename instead of being really new :)

-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer    meebey at meebey.net  http://www.meebey.net/
PEAR Developer    meebey at php.net     http://pear.php.net/
Debian Developer  meebey at debian.org  http://www.debian.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-mono-devel/attachments/20080615/4ee4a289/attachment.pgp