Hello porters, This may be a silly question. The porters handbook and bsd.port.mk man page suggest that version is set to 0.0 and then it is incremented as software develops and so on. This stuff I understand.
As far as I dig information, the libraries are then installed as libfoo.so.0.0 and to get this working is matter of testing and fidling the build process. Now comes the tricky part. Someone finds a bug. It gets fixed in svn and when I set the library version to wrong number, consumer says the library is incompatible. And this is sane thing. Using old and broken library is stupid, loses work and makes you angry. But for the finder of the bug, the ported library is useless. And the bug fix stays untested. After that I would get the blame of broken package. When I work on the port side of the consumer programs, I can take care of this problem. However how to handle the non-ported build? And there are no unportable things like GNU or libtool. Maybe pkg-config in configure as fallback for dependencies. And if someone is interested, I'm working on Ringdove suite. Librnd, pcb-rnd, camv-rnd and sch-rnd. Best regards, Hannu Vuolasaho P.S. What the comment on SHARED_LIB line means?
