I was honestly thinking of stuff like `du` (disk usage), `cp`, `mv`, and the like. Like I sort of mnemonically remember them, compared to mentally mapping `convert` -> imagemagick.
I didn't say it was developed on/for Linux.
But because it was a mature product and added to Linux very early on, this is why it was able to get the names that it did.
so maybe you can share what it is you are responding to?
To be quite clear, in the context of ImageMagick, claiming early Linux image processing with ImageMagick is irrelevant, also, not exactly true. What much does alleged Linux inclusion of any application (/usr/local/*) whatsoever have to do with that application? You're apparently promoting Linux by claiming it's a feat few had considered, or otherwise saying "I am cool," which is fine I guess and I don't doubt it, but also irrelevant.
As I pointed out, ImageMagick was developed in 1987, and I should have gone on to specify that most digital image manipulation techniques were developed in the 1960's. So assuming your Yggdrasil installation was processing images with it in early 1993, that it was "before most had considered it" is hardly knowable. I'm reading it similarly to saying your Chevy wipers were wiping your windshield before most had considered it when modern wipers were invented 50 years ago and all the techniques for doing so were worked out around the turn of the century. Chevy's are great and all, but there are other things.
It is at relevant, because this is about why imageMagick has such prime namespace on linux.
I don't have any idea why you are going in these seeming random directions, I'm not promoting linux, or whatever else your going on about.
This is my original statement
> Image magick has been around for a pretty long time, and was doing image processing on linux before most had considered it.
Surely we can both agree part below is a fair and accurate statement
> Image magick has been around for a pretty long time
This next part, is the part that seemingly needs clarification
> and was doing image processing on linux before most had considered it.
When imagemagick was added to linux in the mid 90s (near ImageMagick 4) not a lot of people were doing image processing in the OS. and being that it was the first mature image processor added to the distro, it is why it has the namespaces it does.
I'm not sure how you are either not getting that clarifier of "on linux" and seem to be trying to debate something about the history of image processing itself?
To be very clear, and to hopefully prevent this continued necro'ing of this post, I was not, talking about this history of image processing, but the specific linux namespace that imagemagick has, and why it has it.
Any other points of debate about this are irrelevant.
$ pacman -Ql imagemagick | grep bin
imagemagick /usr/bin/
imagemagick /usr/bin/Magick++-config
imagemagick /usr/bin/MagickCore-config
imagemagick /usr/bin/MagickWand-config
imagemagick /usr/bin/animate
imagemagick /usr/bin/compare
....
You may also enjoy: $ pacman -Qo /usr/bin/{display,convert}
/usr/bin/display is owned by imagemagick 7.1.0.16-1
/usr/bin/convert is owned by imagemagick 7.1.0.16-1 $ dpkg -L imagemagick-6.q16 | grep bin
/usr/bin
/usr/bin/animate-im6.q16
/usr/bin/compare-im6.q16
/usr/bin/composite-im6.q16
/usr/bin/conjure-im6.q16
/usr/bin/convert-im6.q16
/usr/bin/display-im6.q16
/usr/bin/identify-im6.q16
/usr/bin/import-im6.q16
/usr/bin/mogrify-im6.q16
/usr/bin/montage-im6.q16
/usr/bin/stream-im6.q16
Similarly, you get $ dpkg-query -S /usr/bin/convert-im6.q16
imagemagick-6.q16: /usr/bin/convert-im6.q16
This does not work for the canonical executables though as they are just symlinks to /etc/alternatives/foobaryou can use realpath for this
dpkg -S $(realpath /usr/bin/convert)
and you can ignore the path to it entirely with dpkg -S $(realpath $(which convert))