Hi Jon, Am 20.07.2011 um 21:07 schrieb Jonathan Craig: > Non-Unique SONAMEs) Bad developer, bad. Oh well, the packager must > still deal with it. I'm not sure of an example package like this to > check against my ubuntu catalog.
The old libnet.so > This situation calls for either > making the versions exclusive (using conflicts with) or configuring > them for there own tree. Using alternatives is a risky undertaking > because it will almost always eventually cause grief. If alternatives > puts the .so in a common lib directory and a user builds against it > then changes the alternative choice, whatever they've built will > break. The only viable solution is to fix that and to force a unique soname. This is what we have done on libnet1. Best regards -- Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
