[Pkg-javascript-devel] Request for policy interpretation: procedure and possible outcomes for naming conflicts

Jérémy Lal kapouer at melix.org
Thu May 3 09:58:39 UTC 2012


On 03/05/2012 11:51, Bill Allombert wrote:
> On Wed, May 02, 2012 at 04:20:47PM -0500, Jonathan Nieder wrote:
>> Bill Allombert wrote:
>>> On Wed, May 02, 2012 at 02:12:22PM -0500, Jonathan Nieder wrote:
>>
>>>>   Policy also states that different packages must not install commands
>>>>   with different functionality with the same name.
>>>
>>> Such packages would have to Conflicts anyway, and gratuituous conflict
>>> must be avoided. This is not a waivable requiremrent.
>>
>> As a strawman example, here is what I was thinking of when I asked that:
>>
>>  nodejs package adds a "nodejs" command which behaves exactly like "node"
>>  in Debian (this has already been done) and upstream (working on it).
> 
> IMHO, /usr/bin/node is much too generic a name to be in any package.

Objection: a lot of very generic command names are in /usr/bin.

Jérémy.




More information about the Pkg-javascript-devel mailing list