Following up from Jani's mail regarding pecl picking,
I will be tweaking CVSROOT/modules later tonight so that
our "golden" pecl packages get checked out along with the
php sources.
This includes removing the symlink that links pecl/sqlite
into ext (as it would be redundant).
Once the change is made, you will need to check out the source
again to pick up the extensions; you can check out over the top
of your existing working directory and CVS will be smart
enough to only fetch the things you need, so this shouldn't
pose a problem.
This is just an advance warning; nothing has changed yet.
--Wez.
We agreed *not* to rely on modules for this kind of
procedure, because it effectively disables "cvs upd -d".
Please explain what problem you are trying to solve and we
will find an alternative.
- Sascha
Following up from Jani's mail regarding pecl picking,
I will be tweaking CVSROOT/modules later tonight so that
our "golden" pecl packages get checked out along with the
php sources.This includes removing the symlink that links pecl/sqlite
into ext (as it would be redundant).Once the change is made, you will need to check out the source
again to pick up the extensions; you can check out over the top
of your existing working directory and CVS will be smart
enough to only fetch the things you need, so this shouldn't
pose a problem.This is just an advance warning; nothing has changed yet.
--Wez.
The adding of modules happens VERY rarely.
So your "disables cvs upd -d" is not very good argument
against this. And there is no alternative way anyway..
If you know such, PLEASE do tell us. :)
--Jani
We agreed not to rely on modules for this kind of
procedure, because it effectively disables "cvs upd -d".Please explain what problem you are trying to solve and we
will find an alternative.
- Sascha
Following up from Jani's mail regarding pecl picking,
I will be tweaking CVSROOT/modules later tonight so that
our "golden" pecl packages get checked out along with the
php sources.This includes removing the symlink that links pecl/sqlite
into ext (as it would be redundant).Once the change is made, you will need to check out the source
again to pick up the extensions; you can check out over the top
of your existing working directory and CVS will be smart
enough to only fetch the things you need, so this shouldn't
pose a problem.This is just an advance warning; nothing has changed yet.
--Wez.
The adding of modules happens VERY rarely. So your "disables cvs upd -d" is not very good argument against this. And there is no alternative way anyway.. If you know such, PLEASE do tell us. :)
The symlinks are the only transparent way.
Remember the big fight with James about this issue? He
wanted to do the same thing as Wez is proposing.
- Sascha
On Thu, 4 Dec 2003 16:00:47 +0200 (EET)
Jani Taskinen sniper@iki.fi wrote:
The adding of modules happens VERY rarely. So your "disables cvs upd -d" is not very good argument against this. And there is no alternative way anyway.. If you know such, PLEASE do tell us. :)
Keep them in PECL and work on a per release basis (and avoid these
annoyed MFH and related things :D )? or aka php5-bundle definitions
described by Edin.
Then it should be easy to call 'pear bundle' (or alter this command
to fit our needs) to generate the release files for sources distros or
snaps. CVS users can add manually the required symlinks if they like to
use the respective head of each extension branches.
OK I'm off ;-)
pierre