I'm writing a package for libxml++, and it has the strange particularity that the package won't compile if there is an older version of libxml++ present on the system. This is due to the building of tests with both link flags : -L/sw/lib -L../../libxml++/.libs This has a bad consequence because it tries to link the examples against the old library instead of the one we're trying to build and fails at this point.
I have not seen any other case for such a problem in the Fink ML, although
the behaviour of Fink is to build the new package before uninstalling
the older one.
Nevertheless, I really don't know what I should do here, nor whether this is a known issue (and there is a smart way to handle it) or whether this behaviour is quite rare :
I've been looking for solutions but :
- ./configure doesn't provide an option to build only the lib and not
the examples.
- Is it possible to include this kind of 'intern' conflicts in the Conflicts tag
providing a version of the same package that conflicts with the version
we're trying to install ? "Conflicts: libxml++-0.27.0 or libxml++ (=<0.27.0)" ?
However, even if Fink handle this, it wouldn't be very user-friendly as it
would force the user to manually uninstall the older package before
updating to the new one.
- Any others options ?
Sorry for the so long mail, Cheers
Olivier Bonnet
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
