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

Bug#849493: RFS: vc/1.3.0-1 [ITP]



Hello Aleksey Samoilov,

Thanks for your interest in packaging for Debian.... 

On Wed, Dec 28, 2016 at 05:59:36AM +0900, Aleksey Samoilov wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "vc"
[...]
>   Alternatively, one can download the package with dget using this command:
> 
>     dget -xhttps://mentors.debian.net/debian/pool/main/v/vc/vc_1.3.0-1.dsc
> 
> 
>   Changes since the last upload:
> 
>   vc (1.3.0-1) unstable; urgency=medium
> 
>   * Initial release (Closes: #846491)

I reviewed your package and it generally looks good.

Minor comments:
 - not sure if enabling verbose dh is something I'd do by default.
 - dh compat 10 is the latest, not that it would buy you anything
   practically but staying with the current revision is usually
   a nice anyway.
 - you forgot to retitle #846491 to ITP (replacing RFP) and
   set yourself as owner.

Over to the issue that didn't just make me sign and upload it:
In Debian we have one shared namespace for all packages (and
potential binaries, etc.). Shorter names often leads to
collisions in the namespace.
I don't see any other package currently named "vc" but still
staying away from any 2letter name would in my opinion be
preferrable. Atleast unless the name is obvious for most
people and I think that's not the case here. For example
myself (and likely many else) would being presented with
only "vc" think it's about "virtual consoles".
Certain things in the archive resolves the problem with the
global debian namespace while still somewhat retaining their
original name by adding a prefix, like eg. python-foo for
what the python world generally knows as only 'foo'.
Maybe you could consider renaming (both the source and binary)
packages to simd-vc(-dev) or something similar?

Please let me know what you think. (And a happy new year
to you!)

Regards,
Andreas Henriksson


Reply to: