incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: handling of ext_sources - Juergen's suggestion [was: Re: A systematic approach to IP review?]
Date Thu, 22 Sep 2011 17:10:56 GMT
You can get anything off of the web interface of SVN at the individual level without it being
in a working copy, though of course it has to be somewhere local while it is being processed
in a build.

But if you check-out the trunk, you get everything that is in the trunk HEAD (or a specified)

As far as I know, you can do a check-out anywhere deeper in the tree and avoid everything
not at that node [and below].  For example, just checkout trunk/main.  

It takes some consideration of SVN organization to have the desired flavors in convenient
chunks that people can work with without having to eat the whole thing (with regard to SVN
checkout, SVN update and, of course, SVN commits).  I can testify that an SVN UDPATE of the
working copy of the entire incubator/ooo/ subtree is a painful experience, even when there
is nothing to update.

 - Dennis

PS: I find it an interesting characteristic of SVN that trunk, tags, and branches are just
names of folders and don't mean anything special to SVN.  The nomenclature and it is use is
a matter of custom, like code indentation rules for ( ... }.

-----Original Message-----
From: Rob Weir [] 
Sent: Thursday, September 22, 2011 05:24
Subject: Re: handling of ext_sources - Juergen's suggestion [was: Re: A systematic approach
to IP review?]

2011/9/22 Pavel Janík <>:
>> Proposed way to move forward
>> 1. put the externals under .../trunk/ext_sources
>> .../trunk/ext_sources
>> .../trunk/main
>> .../trunk/extras
>> 2. adapt configure to use this as default, disable the download (maybe
>> reactivate it later if we move to a DSCM)
>> 3. keep the process with checking the md5 sum as it is (for potential later
>> use)
>> Any opinions or suggestions?
> +1.
> And one more question:
> If we put something into SVN into .../trunk/ext_sources, do we have some URL that can
replace http://hg.... so users don't have to check out everything? Ie. do we have a URL where
we have "real checkout" of the SVN? Some SVN web interface? Don't know Apache infra well yet...
That would be real killer solution!
> --

I was thinking something similar.  We only need to use the SVN
interface to the files when we're adding or updating.  But we can have
bootstrap continue to download via http.  The location, using
Juergen's proposed location, would be

This would save having a duplicate local SVN working copy of the file, right?


View raw message