Overlapping images

["Markus W. Weißmann"]

On 29 Apr 2010, at 08:09, Ryan Schmidt wrote:

> On Apr 29, 2010, at 00:36, Andrea D'Amore wrote:
> 
>> while installing "compare" port I bumped into this error:
>> 
>> --->  Activating compare @1.16_1
>> Error: Target org.macports.activate returned: Image error:
>> /opt/local/bin/compare is being used by the active ImageMagick port.
>> Please deactivate this port first, or use 'port -f activate compare'
>> to force the activation.
>> 
>> 
>> Seems ImageMagick and compare have the same name for their tool, is
>> there a specific policy in such a case or how do you suggest to solve
>> it?
> 
> It looks like the latest version of compare is 1.16 which is from 2004, and it doesn't have a homepage (at least not defined in the port), while ImageMagick's homepage is voluminous and the software is actively developed, sometimes releasing several new versions a week. So I say ImageMagick wins. :) Maybe I'm also biased because I'm the ImageMagick maintainer and I use ImageMagick all the time, whereas I had not heard of this other compare tool until you just mentioned it.
> 
> I guess the policy is that the maintainers of the conflicting ports should work out what should be done. I marked the ports as conflicting for now. We could change the compare port so it installs the file under a different name or in a different location to resolve the conflict. Markus, what do you think we should do?
> 

I second that -- and have just renamed the executable and manpage of 'compare' to 'scompare' (in the spirit of the author of 'compare' -- Mr. Schillings --  naming convention; his 'make' is e.g. called 'smake').
Revision 2 is the renamed one.


Regards

-Markus

--
Markus W. Weissmann, M. Sc.
http://www.macports.org/
http://www.mweissmann.de/