Re: execline/imagemagick namespace collision
Gerrit Pape <[email protected]> Wed, 11 Feb 2004 21:07:46 +0000
| Newsgroups | gmane.comp.djb.package |
|---|---|
| Message-ID | <20040211210645.13106.qmail@9c18f81881e769.315fe32.mid.smarden.org> |
On Wed, Feb 11, 2004 at 09:44:29PM +0100, Laurent Bercot wrote: > > Hi, the /command name "import" is allocated for the execline package. > > Unfortunately the imagemagick package also provides a command "import", > > ImageMagick provides a lot of "generic" command names, which don't > fit well in a global naming scheme. The problem has been reported to > them more times than I can remember ; AFAIK, they didn't answer. Well, you can say the same for the execline package. It uses command names like import, cd, define, exec, exit, export, if, shift, wait, puts them into /command, and actually should also put them into /usr/local/bin according to http://cr.yp.to/slashpackage/management.html > Most people I know prefix the ImageMagick command names with "IM", > so that there's no confusion. Another approach, better suited to > the /package way, might be to always use the explicit path : > /opt/ImageMagick/bin/import vs. /package/admin/execline/command/import. I would rather see the conflict resolved differently. Regards, Gerrit. -- Open projects at http://smarden.org/pape/.