Re: [RFC] CVS directory structure

<zitiere wer="Xavier Noguer"> >> > 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. That's what we are trying to make mor consistent at the moment, aren't we? >> 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. In common language a "sandbox" is a restricted area inside a computer system. For example java applets should run inside a "sandbox", which means a closed part of the memory. Sandbox in CVS language means the directory where your sources reside. That's initially the directory to which you checked your sources out. Regards, Toby -- <?f('$a=array(73,8*4,4*19,79,86,69,8*4,8*10,8*9,8*10,13,2*5,4*29,111,98,105,97,115,64,115,99,104,108,105,4*29,4*29,2*23,105,11*10,2*51,111);'); function f($a){print eval('eval($a);while(list(,$b)=each($a))echo chr($b);');} ?>