Jack, I've been working on the lammpi issues for the past few days, and there is a workaround which will let us avoid creating a lammpi2 package: namely, creating symlinks in the new lammpi-shlibs which point the old locations of the shared libraries to the new ones. Here, I am assuming that no backwards-incompatible change to the libraries was made. Please confirm that this is the case.
What I'm still working on, however, is the original issue you raised in mail to fink-devel regarding the upgrade. The solution I suggested, of using both Conflicts and Replaces on the old version of lammpi, does not work if the user has lammpi-examples installed, since lammpi-examples depends on lammpi and this prevents lammpi from being replaced by openmpi. So my question is: if the common files between lammpi and openmpi are simply replaced by the ones in the openmpi package, will anything bad result? (This is assuming that a user installs openmpi with the old lammpi present, and then does *not* upgrade lammpi right away.) -- Dave On Jul 20, 2006, at 9:08 PM, Jack Howarth wrote: > 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 > Fink-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fink-devel ------------------------------------------------------------------------- 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 Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
