Re: policy for source package names
On 08/05/2014 12:04 AM, Vincent Cheng wrote:
> On Mon, Aug 4, 2014 at 2:17 PM, Antonio Valentino
> <antonio.valentino@tiscali.it> wrote:
>> Hi list,
>> I read in [1] and [2] that binary packages with public modules should
>> have the python- (or python3-) prefix in the name.
>> I'm wondering if the same naming rules should be used for source packages.
>>
>> I'm preparing some new packages so I would like to be sure I'm using the
>> correct naming before the first upload.
>>
> AFAIK, no, there aren't any hard and fast rules regarding source
> package names. In fact, I don't think there are any rules at all; just
> don't pick a source package name that's already taken, and pick one
> that is relevant to your package (if you take a look at existing DPMT
> packages [1], most of them either use their module name, or prefix it
> with python-).
We have discussed some times about this in different groups (DebianMed
Debian Java ....).
I think that usual way is to use for source package the name of the
upstream software (if not already taken of course and matching general
name rules).
Olivier
> Regards,
> Vincent
>
> [1] https://qa.debian.org/developer.php?login=python-modules-team@lists.alioth.debian.org
>
>
>
> --
> gpg key id: 4096R/326D8438 (keyring.debian.org)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Reply to: