[csw-maintainers] A policy issue

Philip Brown phil at bolthole.com
Wed Feb 18 18:22:08 CET 2009


On Wed, Feb 18, 2009 at 04:35:05PM +0100, Roger Håkansson wrote:
> ..., but also they have removed a bit of code in ilmbase (actually they 
> did it already in openexr-1.4, where the current is 1.6 and CSW-current 
> is 1.2) which makes it impossible to compile on Solaris 8 and Solaris 9, 
> due to nonexistant floating point arithmetic funktions (sinf,cosf...).

"impossible"? not at all. there are fairly easy workarounds for that sort
of thing.


> 
> As I see it, the possible solutions are:
> 
> - Keep compiling imagemagick against current CSWopenexr, with the 
> possible implication that we might have to drop openexr-support in the 
> future when imagemagick requires an newer openexr-version

if it works with the current version, that's fine with me. 
that being said...


> - Backport the old code which upstream removed, as a "CSW-patch" with 
> the implication that it might have some impact on 
> openexr-stability/functionality (in this case, the "backport" consists 
> of an ifdef/else with two different C++-templates, where one uses 
> asin/cos/sin and the other asinf/cosf/sinf, so it should work, but we 
> never know what the ILM-guys might do in the future).

This sounds fairly trivial, and also pretty future-proof.

> The question is which solution is the preferred one?

The latter. (2nd)




More information about the maintainers mailing list