Re: policy for source package names

[Hans-Christoph Steiner <hans@at.or.at>]

Barry Warsaw wrote:
> On Aug 05, 2014, at 04:09 PM, Hans-Christoph Steiner wrote:
> 
>> I think it is a good practice to make the source package name the same as the
>> binary package name as long is there isn't a good reason to do otherwise.  So
>> with any source package that produces one binary package, those names should
>> match.  That keeps the Debian namespace smaller and more easy to understand.
>>
>> If a source package produces more than one binary package, then I think it
>> makes the most sense to name the source package using the upstream name,
>> barring name conflicts, too general a name, etc.
> 
> In the context of Python libraries, please try to be pro-active, especially if
> you know that the upstream is or will be supporting both Python 2 and 3.
> 
> plan-for-success-ly y'rs,
> -Barry

I suppose I was being too general.  For python packages, I generally use the
python- form for both the source and python2 package.

.hc