Dave,
Renaming the package at this point would likely cause more
far breakage than it would resolve. There are only a couple of
packages that use lammpi currently and they have all been
version bumped to required the newer packaging. If we rename
the the new lammpi, we would have forcibly regress everyone
who has the new lammpi installed back to the old packaging
and then regress all the software as well. It will cause far
more grief than it would solve. In general, everyone will want
to move to the new packaging to get both the newer lammpi
release and the ability to use openmpi side by side. If they
are using 'fink selfupdate' and 'fink update-all', all the
packages that use lammpi are automatically upgraded to versions
that require the new packaging.
Jack
ps On the other hand, anyone who relies on file locations in
fink packages for software built outside of fink is nuts and
shouldn't have any expectations.
-------------------------------------------------------------------------
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
