Everything
php
Learn Community Releases The PHP Project
Home » Project » Newsgroups » php.internals » Problem updating CVS HEAD »

Problem updating CVS HEAD

php.internals

Pasha Zubkov

21 years ago
Hi list, If after `... checkout php-src` I go to directory php-src and remove ZendEngine2 directory, then run `... up -APd` don't restore this directory from repo. How I can update my copy to repo status? CVS client 1.11.20

Jani Taskinen

21 years ago
On Thu, 4 Aug 2005, Pasha Zubkov wrote:
> Hi list, > > If after `... checkout php-src` I go to directory php-src and remove > ZendEngine2 directory, then run `... up -APd` don't restore this > directory from repo. How I can update my copy to repo status?
Do NOT remove the directory. buildconf handles this. --Jani

Pasha Zubkov

21 years ago
Jani Taskinen wrote:
> On Thu, 4 Aug 2005, Pasha Zubkov wrote: > >> Hi list, >> >> If after `... checkout php-src` I go to directory php-src and remove >> ZendEngine2 directory, then run `... up -APd` don't restore this >> directory from repo. How I can update my copy to repo status? > > > Do NOT remove the directory. buildconf handles this. > > --Jani >
I know that this directory is engine and it's nedded, but why it's not recovered by `... ud -d`?

Antony Dovgal

21 years ago
On Thu, 04 Aug 2005 15:24:07 +0300 Pasha Zubkov <pasha.zubkov@gmail.com> wrote:
> Jani Taskinen wrote: > > On Thu, 4 Aug 2005, Pasha Zubkov wrote: > > > >> Hi list, > >> > >> If after `... checkout php-src` I go to directory php-src and remove > >> ZendEngine2 directory, then run `... up -APd` don't restore this > >> directory from repo. How I can update my copy to repo status? > > > > > > Do NOT remove the directory. buildconf handles this. > > > > --Jani > > > > I know that this directory is engine and it's nedded, but why it's not > recovered by `... ud -d`?
Re-read Jani's reply. Do not touch anything, ./buildconf does it for you automagically.
-- Wbr, Antony Dovgal

Pasha Zubkov

21 years ago
Antony Dovgal wrote:
> Re-read Jani's reply. > Do not touch anything, ./buildconf does it for you automagically. >
If I modified source, maybe delete some directories ;), and after this I want to update source to repo status. "why it's not recovered by `... ud -d`?"

Derick Rethans

21 years ago
On Thu, 4 Aug 2005, Pasha Zubkov wrote:
> Antony Dovgal wrote: > > Re-read Jani's reply. > > Do not touch anything, ./buildconf does it for you automagically. > > > > If I modified source, maybe delete some directories ;), and after this I > want to update source to repo status. "why it's not recovered by `... ud > -d`?"
It's a CVS problem - it doesn't resolve repository links with upd, only on checkout. Derick

Pasha Zubkov

21 years ago
Derick Rethans wrote:
> It's a CVS problem - it doesn't resolve repository links with upd, only > on checkout. > > Derick >
Maybe sputid question, but why PHP stil use CVS instead of SVN?

Derick Rethans

21 years ago
On Thu, 4 Aug 2005, Pasha Zubkov wrote:
> Derick Rethans wrote: > > It's a CVS problem - it doesn't resolve repository links with upd, only > > on checkout. > > Maybe sputid question, but why PHP stil use CVS instead of SVN?
How do you want to convert 1100 users instantly without causing disruptions? Derick

Jochem Maas

21 years ago
Derick Rethans wrote:
> On Thu, 4 Aug 2005, Pasha Zubkov wrote: > > >>Derick Rethans wrote: >> >>>It's a CVS problem - it doesn't resolve repository links with upd, only >>>on checkout. >> >>Maybe sputid question, but why PHP stil use CVS instead of SVN? > > > How do you want to convert 1100 users instantly without causing > disruptions?
magicwand.php

Andrey Hristov

21 years ago
Pasha Zubkov wrote:
> Derick Rethans wrote: > >>It's a CVS problem - it doesn't resolve repository links with upd, only >>on checkout. >> >>Derick >> > > > Maybe sputid question, but why PHP stil use CVS instead of SVN? >
Because CVS works and ppl are so far happy with it Andrey

Pasha Zubkov

21 years ago
Andrey Hristov wrote:
> Because CVS works and ppl are so far happy with it > > Andrey >
CVS don't always work properly. This example shows it ;) Also SVN has better versioning control mechanism. Hope sometime in the future php will "update" to SVN, so why not now?

Derick Rethans

21 years ago
On Fri, 5 Aug 2005, Pasha Zubkov wrote:
> CVS don't always work properly. This example shows it ;) Also SVN has > better versioning control mechanism. Hope sometime in the future php > will "update" to SVN, so why not now?
SVN has other annoyances. We will not move anytime soon. (period) Derick

Jani Taskinen

21 years ago
On Fri, 5 Aug 2005, Pasha Zubkov wrote:
> Andrey Hristov wrote: >> Because CVS works and ppl are so far happy with it >> >> Andrey >> > > CVS don't always work properly. This example shows it ;) Also SVN has
It works fine as long as you don't try to outsmart it.
> better versioning control mechanism. Hope sometime in the future php
SVN is far from better.
> will "update" to SVN, so why not now?
Over my smoking carcass.. --Jani

Andi Gutmans

21 years ago
It's a love-hate relationship with CVS :) At the end of the day, it works and with the investment we have in CVS scripts there are not enough problems to give us enough motivation to move to anything else. Andi P.S.- Clearcase would change my mind :)