Hi!
> Typically, it shouldn't be installed unless you're doing porting work or
> building a depending package. So the large dependency chain should only
> be a temporary nuisance. At least, that was my reasoning when taking
> this choice, but of course you're very welcome to try and convince me
> otherwise.
I wouldn't have been bothered too much if that was the case :) Many
packages *Depend* (not Build-Depend) on perlmagick, like
findimagedupes or html2ps for example. Now, if the user decides to
shift from ImageMagick to GraphicsMagick, he/she has to use
graphicsmagick-libmagick-dev-compat instead of perlmagick. In this
case, this package serves as an end-user requirement and not as a
developer package. It is not quite right to thrust upon such an user
so many dev packages which he/she might not at all be interested in.
Regards,
Ramkumar.
--
One of the main causes of the fall of the Roman Empire
was that, lacking zero, they had no way to indicate
successful termination of their C programs.
-- Robert Firth
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
