On Jul 20, 2006, at 9:13 AM, Jack Howarth wrote: > Chris, > If I understand fink correctly, adding... > > Replaces: lammpi (<< 7.1.2-1000) > > ...after... > > BuildConflicts: lammpi (<< 7.1.2-1000), lammpi-shlibs (<< > 7.1.2-1000), lammpi-dev > Conflicts: lammpi (<< 7.1.2-1000), lammpi-shlibs (<< 7.1.2-1000), > lammpi-dev (<< 7.1.2-1000) > > for the openmpi package would only achieve deinstalling the older > lammpi package > when the openmpi package is installed. That is okay in my case > because packages > that use lammpi have to be rebuilt because the shared libs in > lammpi are moved > to a subdirectory in the new package.
That's completely against fink policy. You should never move shared libraries without renaming the package which provides them. There is an implicit promise, when a package contains shared libraries that other packages link to, that those shared libraries will remain in place as long as the providing package remains installed _even_if_it_is_updated_to_a_newer_version. If you need to move the shared libraries, please rename the package which provides them to lammpi2-shlibs or some such, and create a stub package for lammpi-shlibs which keeps the old shared libraries in place. That way, someone who updates won't find that their fink installation has broken. -- Dave ------------------------------------------------------------------------- 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
