Re: [RFC] CVS directory structure

Marshall Roch <pear-dev@exclupen.com> escribió > Xavier Noguer wrote: > > I'm -1 on this. CVS is a tool for source control. Doing development > > directly on your CVS dir is a bad idea. > > Can you (or anyone else) support this argument? You can test your code better when it's layout in the filesystem is the same as it will be in production. > Take a look at the CVS best practices from the LDP: > > http://en.tldp.org/REF/CVS-BestPractices/html/section1-devsandbox.html > > Specifically, section 4.4: > > 4.4. Do not work outside the sandbox It is not your CVS or development dir that is your sandbox. It's your whole machine. I fixed a bug recently where a class on my package was trying to allocate 1.6GB bytes of memory. If for some reason PHP didn't control how much memory I can ask, and I were using an OS with mm so broken that it didn't know how to handle such a request (a lot of ifs, I know, but bear with me), I could have crashed my machine easily. Please see point 4.1 in that article. That is _system_ clock. > > The sandbox can be thought of as a controlled area within which CVS > > can track for changes made to the various source files. Files > > belonging to other developers will be automatically updated by CVS. > > Thus the developer who lives within the sandbox will stand to gain a > > lot of benefits of concurrent development. This benefit cannot be > > achieved for work done outside a sandbox. > > It's especially bad to copy files around when you aren't the only person > working on a package. With your dev copy outside of CVS control, how > will you apply bugfixes from other developers? As that article pointed out, check-in often. Xavier http://www.xavier-noguer.com/