I have posted to fink tracking new proposed packaging for a
lammpi2 package and revised packaging for openmpi, gromacs-mpi,
maloc-mpi and apbs-mpi. The changes in lammpi2 involve making the
new package (which is effectively the current lammpi in unstable)
conflict with lammpi. The other packages no longer build against
lammpi but will use lammpi2 instead. The situation with regressing
the current lammpi in unstable is messy since the lammpi in stable
(the old one) doesn't build on macintel which the current lammpi
in unstable does. I think the smartest thing to do is leave the
lammpi in unstable alone and just make sure it doesn't every get
moved into stable. We might want to do one revision of it to
make it conflict with lammpi2 for good measure.
Jack
ps I have absolutely no intention of trying to make lammpi and
lammpi2 coexist. The proposition is absurd since the movement of
the shared libraries was needed to allow multiple mpi implementations
to coexist (and that is the very reason I am forced to create
a lammpi2 package).
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fink-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-devel
