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 binar
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
>m
olivier.sal...@codeless.fr wrote:
>
> On 08/05/2014 12:04 AM, Vincent Cheng wrote:
>> On Mon, Aug 4, 2014 at 2:17 PM, Antonio Valentino
>> 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
On 08/05/2014 12:04 AM, Vincent Cheng wrote:
> On Mon, Aug 4, 2014 at 2:17 PM, Antonio Valentino
> 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
On Tuesday, August 05, 2014 11:54:37 Ben Finney wrote:
> Vincent Cheng writes:
> > […] just don't pick a source package name that's already taken, and
> > pick one that is relevant to your package […]
>
> I further advise: Try to avoid names which are too broad (e.g.
> “coverage” for a Python-spe
Vincent Cheng writes:
> […] just don't pick a source package name that's already taken, and
> pick one that is relevant to your package […]
I further advise: Try to avoid names which are too broad (e.g.
“coverage” for a Python-specific code coverage package), or names which
can easily be anticip
Hi Vincent,
Il 05/08/2014 00:04, Vincent Cheng ha scritto:
> On Mon, Aug 4, 2014 at 2:17 PM, Antonio Valentino
> 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 ru
On Mon, Aug 4, 2014 at 2:17 PM, Antonio Valentino
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 p
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 befor
9 matches
Mail list logo
