I *am* the upstream developer. I *have* read the libtool manual. This *is* the first shared library release. Period. Trust me.
Okay.
Any solution besides this? Any way the packaging interface versioning in fink can let us escape this mess?
Well, not really. If necessary we may have to break things in this case. Since I do not have openbabel installed, I'll have to ask you a question. What is the output of otool -L /sw/lib/libopenbabel.1.dylib ?
Right now, we could put in your openbabel package as libopenbabel.0.dylib, in a package called openbabel0-shlibs, but the problem would come in the future when you want to make libopenbabel.1.dylib upstream :( I'm not quite sure how to feal with that one yet. Never fear though, we'll come up with something :)
Peter -- Peter O'Gorman - http://www.pogma.com
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
