Re: PECL versioning

Hi Pierre,

I don't understand this question.

This was also an off-list discussion between Chris, you and myself until now, so nor will anybody else understand this question because nobody else knows what we're talking about in the first place. The conversation went:

OCI8 currently uses PHP_OCI8_VERSION to mean the version of the Oracle libraries. (Chris)

I think basically that tells you what we're up against when it comes to versioning PECL distributions. There needs to be a hard and fast rule about it, and I personally think PHP_*_VERSION for the extension and *_VERSION for the underlying library makes the most sense and should cause the least pain. (me)

You replied: There may have conflicts and force one to add more ifdefs. It can be easily fixed using: PHP_[EXTENSIONNAME]_VERSION : Extension Version PHP_LIB[LIBRARYNAME]_VERSION : Library Version Where EXTENSIONNAME and LIBRARYNAME are likely to be the same. The PHP_ prefix is important, something else is not under our "control" and can create conflicts (and #ifdef mess). and I agreed with you. Now you're backtracking and agreeing with what I said in the first place. I'm still looking at the way people use versioning currently in PECL (or don't, as the case may be). I've found four packages so far that actually do what I'm hoping they'll all do! - and one that uses the dodgy rewrite trick during package release. - Steph