Re: PECL versioning

From: Date: Thu, 20 Mar 2008 01:33:08 +0000
Subject: Re: PECL versioning
References: 1 2 3 4  Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-5197@lists.php.net to get a copy of this message
You misread me. It does address the problem pretty well. One only has to define the replace rule in the package.xml for each required files (or only for the .h if it is done in a cleaner way). That does not help much for the rc but as Olivier said, it should not be hard to automatically generate it out of the package.xml.
Erm... are you telling me you want to generate both phpinfo() data and RC data for both snaps and releases from package.xml? Will you excuse me if I go to sleep for a bit?
It is not way too complicated. It is possible (and relatively easily) to allow that once the base is in place.
It's making a process far more complex than it should be, hence 'way too complicated'.
I think what's going to happen is we're going to have to insist that every PECL package defines PHP_*_VERSION in php_*.h, to be honest. And we need to insist that -dev is used there at all times other than during a release.
That is indeed a good solution, and this define can be replaced at package time using the package.xml info (for the releases). For snapshot using cvs (yes that's not your goal but it has to be solved at the same time),
That's exactly my goal. Hence the entire thread to date. it can be manually define, not sure what is the
most developer friendly way.
Pierre. When you roll a release, you remove '-dev'. Then you bump the version. That should *never* be automated!
I will add my docs to the wiki during the weekend.
Go ahead. I still probably won't find them there :) - Steph


« previous php.pecl.dev (#5197) next »