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

David Paleino d.paleino at gmail.com
Sun Jun 15 17:29:40 UTC 2008


On Sun, 15 Jun 2008 19:22:53 +0200, Mirco Bauer wrote:

> 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.

OK, understood.

> 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).

Ok, great.

> 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 :)

I was talking about changing name to the *source* package. To Debian, that
would be a different tarball -- it could even be a different software --, so it
*must* go through NEW.
However, I know that renames are usually faster :)

Thanks for the explanation,
David

-- 
 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-mono-devel/attachments/20080615/16da0bd2/attachment.pgp 


More information about the Pkg-mono-devel mailing list