But this is bad because the upstream code is now defining (in v. 1.100.2)
/usr/local/libs/libopenbabel.0.0.0.dylib
This would appear to have no versioning information at all. Is this version completely binary compatible with all previous versions? If not you should send the upstream authors off to read the library interface versions section of the libtool manual.
because of course the shared lib version number should *not* be the same as the package version.
Indeed not, but it also should not be zero unless the library has not changed one iota since the first release (highly unlikely).
Any advice? Any other pointers or reading material for a new package maintainer?
Well, you will have to hack the makefile again to make a compatibility and current version that is greater than the shared library built by the current package. Read the packaging manual and put the updated package on the submissions tracker. If there are errors in the package a fink developer will tell you about them, you'll revise the package etc. etc.
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
