Re: execline/imagemagick namespace collision

On Wed, Feb 11, 2004 at 09:44:07PM +0100, Laurent Bercot wrote:
> > Hi, the /command name "import" is allocated for the execline package.
> > Unfortunately the imagemagick package also provides a command "import",
> 
>  Most people I know prefix the ImageMagick command names with "IM",

Is <URL:http://cr.yp.to/slashcommand/used> supposed to only contain the
"pure" command names the are created compiling and installing from a
package's tarball or also the modifications used by different
distributions to solve these naming conflicts?
Such things like the above 'IM' prefixing.

Should it contain the command names that are additionally installed by a
distribution and which would not be installed when compiling from source
without modifications?
Lots of packages provide 'contrib' directories that contain programs
which are not installed using 'make install' but they are installed by
some distributions packaging systems.

Sould it contain the versioned command names some packages are
installing (either compiled from source or used by different
distributions)?
A versioned perl binary is installed compiling from source.
Debian installs autoconf2.13 and autoconf2.50.


I have written a shell script that scans $PATH for commands that are not
registered in <URL:http://cr.yp.to/slashcommand/list.html> and
<URL:http://cr.yp.to/slashcommand/used>.
The output is quite huge starting it on a "normal" Debian system:
#v+
[email protected]:~ > check-used_commands | tee used
[...]
822-date dpkg-dev
B sam
CDE2Xfcepal xfce
Esetroot eterm
Etbg eterm
Etbg_update_list eterm
Etcolors eterm
Eterm eterm
Etsearch eterm
Ettable eterm
GET libwww-perl
HEAD libwww-perl
[...]
ctags.emacs20 emacs20
ctags.emacs21 emacs21
ctags.xemacs21 xemacs21-bin
[...]
[email protected]:~ > wc -l <used
   1677
#v-
(No. I'm not the maintainer of that system. :-)

Should all these be listed on <URL:http://cr.yp.to/slashcommand/used>?


> 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.

Then you would not need /command at all.
This really would be the cleanest solution AFAICS (and thus perhaps
could or should be used if one slashpackage program is using commands
from another slashpackage program) but it's a bit inconvenient to use in
interactive shells etc. ;-)

Regards,
 Thomas