[70035] trunk/dports/graphics/ImageMagick/Portfile

[Eric Hall]

On Tue, Jul 27, 2010 at 11:57:40AM -0500, Ryan Schmidt wrote:
> 
> On Jul 27, 2010, at 11:50, Eric Hall wrote:
> 
> > On Tue, Jul 27, 2010 at 09:33:09AM -0700, ryandesign at macports.org wrote:
> >> Revision: 70035
> >>          http://trac.macports.org/changeset/70035
> >> Author:   ryandesign at macports.org
> >> Date:     2010-07-27 09:33:08 -0700 (Tue, 27 Jul 2010)
> >> Log Message:
> >> -----------
> >> ImageMagick: delete +perl variant; use p5-perlmagick instead
> > 
> > 
> > 	Please revert this change.  p5-perlmagick has had a
> > very poor track record for staying current with ImageMagick,
> > in fact right now its not current (ImageMagick is at 6.6.3-0,
> > p5-perlmagick is freshly upgraded to 6.59 (aka ImageMagick 6.5.9-1).
> > 	In fact, my suggestion is to remove the p5-perlmagick
> > port and aim people to using ImageMagick +perl if they want
> > the perl<-->ImageMagick interface.
> 
> I don't really want to, because I want ImageMagick's perl interface in a separate port so it can be depended upon and installed separately. p5-perlmagick now compiles again and hopefully it even works.
> 
> The alternative is to switch the p5-perlmagick port to use the perlmagick source that's part of the ImageMagick source code. I really didn't understand why there was a separate p5-perlmagick release at all when the code is already in the ImageMagick sources, and presumably there it's up to date. I worked on trying to use that source instead, but got stuck trying to figure out how to get all the necessary changes into Makefile.PL. I can open a new ticket and attach my efforts so far; maybe someone else can get further with it.
> 
> 

Ryan-
	Given that p5-perlmagick requires ImageMagick to be installed, why have
a separate port for it (other than the fact that MP doesn't yet have 
variants-in-dependencies)?
	As well, saying "hopefully it even works" doesn't give a lot of confidence
that p5-perlmagick is ready for anyone to use it, while I know quite clearly
that ImageMagick +perl works rather well (we use it on a regular basis).

	If the perl interface really has to be pulled out, I think the latter 
(have p5-perlmagick use the ImageMagick perl source) is the correct way to do it.
Otherwise (given the history), there's a continual mismatch between the
ImageMagick version and the p5-perlmagick version, just asking for oddball
issues to crop up.
	How about making a ticket with your efforts to have p5-perlmagick use
the perlmagick source inside of the ImageMagick source code and putting back
ImageMagick +perl until that effort can be completed?
	Of course, if variants-in-dependencies ever gets completed, then
p5-perlmagick could just be a wrapper that depends on ImageMagick +perl.


		-eric