Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50805
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.132 cause and error)
Message-ID: <4CF76EA5.8050403@lsces.co.uk>
Date: Thu, 02 Dec 2010 10:02:13 +0000
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.14) Gecko/20101013 SUSE/2.0.9-2.1 SeaMonkey/2.0.9
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <AANLkTinnOnk2FuxdriyksW4zGGCmauWP7XLBqkTVLMgU@mail.gmail.com> <1291216564.27624.43.camel@guybrush> <AANLkTinTCPeN+cL=YMJST0eEpeshGoJdwEo=FeVBpfOh@mail.gmail.com> <201012020044.26416.larry@garfieldtech.com> <AANLkTin8u1wVDg8Oc35s5cqF132gtRZZnXjMK9rW0Ldc@mail.gmail.com> <4CF762EC.9050207@lsces.co.uk> <AANLkTinF_F=5B6M6CQAhEh4YnxQic-aRN5bVrR74RsvK@mail.gmail.com>
In-Reply-To: <AANLkTinF_F=5B6M6CQAhEh4YnxQic-aRN5bVrR74RsvK@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] git anyone?
From: lester@lsces.co.uk (Lester Caine)

dukeofgaming wrote:
> Its actually faster to use the command line when u have enough practice;
> picture yourself merging branches or something more complicated, I think
> its easier typing stuff as you think it than finding your way around a
> GUI, command line reacts faster than a GUI too. I use the IDE
> integration though, but not the shell integration, at all. I agree on
> visualizing repository tree on the GUI though. In the end its up to each
> individual.

This is the key here.
When working on PHP projects via CVS and SVN I get a view of all the files which 
have changed in the IDE. I can then review those changes and only need to select 
those which do not clash with my own local changes. I can also immediately see 
committed changes that NEED to be rolled back because they DO clash with the 
areas that I am maintaining! Simply automatically merging from the command line 
does not work FOR ME.

DVCS in theory provides a nice way for me to manage my own builds of these 
projects, but the black hole is now how the clash problems are handled as there 
is no easy way to roll back a change that has broken something else. Adding the 
complexity of multiple packages across several projects ... smarty, adodb and 
the like, or building the internal extensions which use libraries from the likes 
of apache, firebird ... in theory should be simplified by the use of a DVCS 
approach, but the reality is that it is still very early days and while people 
are running to a number of camps there needs to be a more tidy integration path 
rather than the current diversity that has been created.

I think that what we actually need is a complete rethink of what the problems 
are ... including managing the user projects rather than JUST raw source code 
... and agree a level of operation rather than the current approach of slagging 
off the paths that you do not agree with. Every package has problems and none of 
them offer a single solution?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php