On 08/29/2010 09:29 AM, Andreas Metzler wrote:
You are already supposed to "change those numbers" (if you make a
release).
The only time you should change the library version number(s) is if the
ABI changes. In other words, if a program that was linked against the
old library will not run if linked against the new one.
Gratuitously changing the library version number(s) creates an enormous
headache for everyone who packages the code.
As for symbol versioning, it can be useful, but is probably overkill for
something like libwraster unless there are plans to change its
internals dramatically down the road. I do agree that not exporting
private symbols is a good idea.
As for where to keep the library version numbers the usual way is to
keep them as #define's in the code. That way if people are doing things
with the code not related to auto* they don't get the dreaded
"unpredictable results."
hth,
Doug (speaking with <hat="FreeBSD windowmaker port maintainer">)
--
To unsubscribe, send mail to [email protected].
