On Jul 15, 2009, at 12:00 AM, Hannes Magnusson wrote:
On Wed, Jul 15, 2009 at 02:23, Philip Olson<phi...@roshambo.org>
wrote:
This diff brings up a good point for us to discuss. What is the
preferred
method to check something out from SVN? Most anything we do
requires at
least two SVN checkouts.
A classic example for English:
- cd /where/doc/stuff/is/stored
- svn co http://svn.php.net/repository/phpdoc/en/trunk phpdoc/en
- svn co http://svn.php.net/repository/phpdoc/doc-base/trunk
phpdoc/doc-base
People have already created these helper modules:
http://svn.php.net/repository/phpdoc/modules/
So in this case the English example changes to:
- cd /where/doc/stuff/is/stored
- svn co http://svn.php.net/repository/phpdoc/modules/doc-en
Everyone feel comfortable with promoting this as our official method?
Which then creates:
- /where/doc/stuff/is/stored/doc-en/en
- /where/doc/stuff/is/stored/doc-en/doc-base
Seems okay. Each translation includes the above plus the language
directory. In IRC we discussed a few potential svn:externals gotchas
including (KSChan also mentioned these):
- They must be manually updated - like when new modules are created or
changed. Although, we rarely add languages so this is a bigger worry
for other parts of php.net, like pecl
- We can't do the following (and no error is given):
--- cd /where/doc/stuff/is/stored/doc-en/
--- svn diff
--- svn commit -m 'changes I made to both doc-base/ and en/'
Not show stoppers here but worth noting and documenting. It's rare
people will want to do the latter, except for let's say adding an URL
(as the entity lives in doc-base) but then again the following does
work:
--- cd /where/doc/stuff/is/stored/doc-en/
--- svn diff en doc-base
--- svn commit en doc-base -m 'changes I made to both doc-base/ and en/'
One thing we shouldn't do anyways is for example commit to both en/
and ja/ in one commit, or phpdoc and php-src...
Regards,
Philip
