Dave,
If you intend to allow lammpi and lammpi2 to coexist, then files
will have to be moved in the old lammpi package. Specifically you will
have to duplicate what I did for the new lammpi and openmpi packages
where the mpicc, mpic++ and mpif77 compilers have been converted into
symlinks which reside in the lammpi-dev and openmpi-dev packages. This
must be done in order to allow the new lammpi and openmpi to build
mpi programs. We will also have to cope with the fact that both the
old and new lammpi want to install man pages in %p/share/man. Frankly
I don't think it is worth the effort. I can insure you that if the
lammpi2 package is created all the existing packages will be immediately
version bumped to use that exclusively. The smart thing to do is just
make lammpi and lammpi2 conflict and force the user to either stick
with the old version or upgrade to the new one. There are limits to
the rationality of legacy support (espcially with an automated build
system in place like fink).
Jack
-------------------------------------------------------------------------
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
