JF,
Actually I think you have that a bit backwards.
Currently the 1.1.5 openmpi packages already have
/sw/lib/openmpi/libopal.0.dylib so this is a
pre-existing situation. The openmpi 1.2.2
packages renames these as libopen-pal.0.dylib and
I created a symlink for backward compatibility.
However, any package using openmpi (1.1.5 or
1.2.2) should be including a BuildConflicts
on opal2 to be on the safe side.
Jack
ps I only see two packages with any mention of
opal2 (other than itself)...
grep opal2 *.info
openh323-1.info:### All following lines are the same as in opal2.info:
pwlib1.info:# the next line also adds -fno-exceptions to the CXXFLAGS for opal2
and openh323-1, through make/ptbuildopts.mak
neither of which has a BuildDepends on opal2. So we are apparently being really
sloppy about maintaining dependencies on opal2. Either that or no one actually
uses it.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Fink-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-devel
