apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tollef Fog Heen <tfh...@err.no>
Subject Re: [VOTE] APR versioning rules w.r.t. released snapshots
Date Fri, 18 Dec 2009 08:02:29 GMT
]] "William A. Rowe Jr." 

I realise I'm somewhat late for the party here.

| Correct, it is internally labeled 1.4.0-dev.  It is not externally (plainly
| visible to the user) as an apr-dev.  The artifact is httpd-2.3.4-alpha-deps.tar
| 
| > from the dev snapshot version bundled with httpd 2.3.4-alpha:
| > #define APR_MAJOR_VERSION       1
| > #define APR_MINOR_VERSION       4
| > #define APR_PATCH_VERSION       0
| > #define APR_IS_DEV_VERSION

Why not also embed the -dev in the soname so the version on disk will be
libapr-1-dev.so.0.4.0 (or whatever the last bits end up being)?  This
would make it possible to install in parallel with what APR is actually
shipping as releases and not break httpd or the hypothetical
crypto-using application that's compiled against 1.4.1.  It's a bit late
to do this to solve the current mess, but making sure that something
like that is set for non-committed ABI and APIs might be a good idea for
the future.

I don't know the exact mechanics you would use for windows and other
non-unixy systems, but I'm sure those responsible for those ports can
come up with something similar.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Mime
View raw message