Re: execline/imagemagick namespace collision

> Well, you can say the same for the execline package.  It uses command
> names like import, cd, define, exec, exit, export, if, shift, wait,

 Yes. You'll admit that execline commands have a more "general Unix"-ish
behaviour than ImageMagick ones ; so I feel the names were justified.


> puts them into /command

 "First come, first served, if you're not asking for something absurd"
seems a reasonable policy to me.


> and actually should also put them into
> /usr/local/bin according to http://cr.yp.to/slashpackage/management.html

 That's a little more debatable. On a correctly administered system,
slashpackagified packages _do not_ use that compatibility thing, and
/command is in the standard PATH. This should be at the sysadmin's
discretion.


> I would rather see the conflict resolved differently.

 AFAICS, there is no conflict in /package strictly speaking :
/command/import is execline's one, and ImageMagick simply doesn't follow
the /package convention.
 There might be some conflict in /usr/local/bin ; this is the
sysadmin's problem, not the /package-guys' problem. I'd advise not
linking execline commands into /usr/local/bin, adding /command to the
standard PATH, and explicitly calling complete ImageMagick paths if you
want ImageMagick commands.

-- 
 Ska