[csw-maintainers] [csw-buildfarm] Rebuild of imagemagick

[John Ellson]

On 06/03/2011 01:35 PM, Philip Brown wrote:
> On Fri, Jun 3, 2011 at 10:27 AM, John Ellson<ellson at opencsw.org>  wrote:
>> I took a look at the 64bit Imagemagick wiki page (nice job, btw).
>>
>> AFAICT the current state of the 64bit builds is:
>>
>>     imagemagick (Roger) depends on
>>         graphviz (John) depends on
>>             ghostscript (John) depends on
>>                 libcups (Dago) depends on
>>                     krb5_lib (Maciej)
>>
>>
>> Is there any status update on krb5_lib and libcups?    Should I be trying a
>> ghostscript 64bit build?
> A side comment:
>
> Sometimes, it is okay to have a 64bit library with "less" features,
> than no 64bit at all.
>
> So, at any point in the chain there, you might make a choice of, "oh
> well, it would be nice to have [gs/cups/krb support] some day, but for
> now, I'm just going to unplug the 64bit pipeline."
> (Although of course, you need to document this very strongly if you
> choose this path)
>
> What makes a good choice of choosing a cutoff point, is when the stuff
> you are chopping is not used by the top level.
> The idea situation being, that , when "someday" comes... since
> imagemagic does not directly use krb5 or cups(?), the library upgrade
> lower down, will be transparent.
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.
>

Yes, I was thinking that it would be easy to drop the ghostscript plugin 
from graphviz.
(Its used to import custom node shapes in PostScript - a feature that 
isn't used much, better to use SVG these days anyway.)

It would also be easy to drop the graphviz dependency from ghostscript.

But, if the goal is to use ImageMagic to drive the creation of a 64bit 
distribution, then there is less point in taking shortcuts.


John