logo       

Re: [PHP-DOC] Preferred doc checkouts: msg#00123

phpdoc

Subject: Re: [PHP-DOC] Preferred doc checkouts

Philip Olson wrote:
>
> On Jul 20, 2009, at 2:56 AM, Hannes Magnusson wrote:
>
>> On Sun, Jul 19, 2009 at 03:26, Rasmus Lerdorf<rasmus@xxxxxxxxxxx> wrote:
>>> Hannes Magnusson wrote:
>>>> Hi guys
>>>>
>>>> Now that we have moved to SVN with slightly changed structure I'd like
>>>> to propose a "standard checkout".
>>>>
>>>
>>> svn co http://svn.php.net/repository --depth empty src
>>> svn co http://svn.php.net/repository/phpdoc/en/trunk --depth infinity
>>> src
>>>
>>> To add another translation:
>>>
>>> cd ~
>>> svn co http://svn.php.net/repository/phpdoc/de/trunk --depth infinity
>>> src
>>>
>>
>>
>> I like it. I like it a lot. :)
>
> The above doesn't work for me (SVN 1.6.3), as I get:
>
> philip@water /tmp> svn co http://svn.php.net/repository --depth empty src
> Checked out revision 284449.
> philip@water /tmp> svn co http://svn.php.net/repository/phpdoc/en/trunk
> --depth infinity src

svn co http://svn.php.net/repository/phpdoc/en/trunk --depth infinity
src/phpdoc/en

will work.

> A few notes and questions:
> - We rarely use branches/tags so it'd be nice if 'trunk' wasn't forced
> in our paths, making it the default... okay?

There is no trunk in the above.

> - When using sparse checkouts, what's the simplest method for having a
> phpdoc-all?

I'd just do a checkout for each language you want. Or do an
"immediates" on phpdoc.

Like this:

svn co http://svn.php.net/repository --depth empty src
svn co http://svn.php.net/repository/phpdoc --depth immediates src/phpdoc

Now you have src/phpdoc with directories for all the languages. But
they haven't been populated yet.

cd src/phpdoc
svn up * --set-depth immediates

Now you have dirs under each language for trunk and all branches/tags
but still not populated

svn up */trunk --set-depth infinity

And now you should have trunk for all languages. But yes, with this
approach you have a trunk directory in your path. It is one of these
things we probably should just get used to with svn and I think it is
probably a good idea to stay close to the actual directory structure of
the repository. You could of course create a directory with symlinks to
hide that a bit.

> - I assume we'd remove our svn:externals while recommending this?

If a svn commit */trunk or something along those lines actually works
with the svn:externals, perhaps it is ok. We don't add languages that
often, so keeping it up to date isn't a big deal in this case.

-Rasmus

Google Custom Search

News | Mail Home | sitemap | FAQ | advertise