Re: Naming standalone module/program

2001-10-31 Thread Donovan Baarda
Quoting Matthias Klose <[EMAIL PROTECTED]>: > Mikael Hedin writes: > > Hi, I'm just finishing my new plucker package. And then I read the > > policy again, and it said I should call my program python2.1-plucker, > > as I use method 2 and the upstream name is plucker. > > Is plucker an applica

Re: Naming standalone module/program

2001-10-31 Thread Anthony Towns
On Thu, Nov 01, 2001 at 11:38:57AM +1100, Donovan Baarda wrote: > Note that additionaly all packages that depend on plucker _and_ python must > use "Depends: plucker, python2.1" and _not_ "Depends: plucker, python (>= > 2.1), > python (<<2.2)". Uh, no, they should *not* do that. Consider what

Re: Naming standalone module/program

2001-10-31 Thread Matthias Klose
Mikael Hedin writes: > Hi, I'm just finishing my new plucker package. And then I read the > policy again, and it said I should call my program python2.1-plucker, > as I use method 2 and the upstream name is plucker. Is plucker an application or a library (probably both ...) > But this is not

Naming standalone module/program

2001-10-31 Thread Mikael Hedin
Hi, I'm just finishing my new plucker package. And then I read the policy again, and it said I should call my program python2.1-plucker, as I use method 2 and the upstream name is plucker. But this is not a module intended to be used by others, only by the programs that comes with plucker. So