subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Corveleyn <>
Subject Re: file externals inside directory externals trouble in 1.6 not 1.7 ?
Date Fri, 01 Feb 2013 09:03:55 GMT
On Fri, Feb 1, 2013 at 12:16 AM, Ward Willats <> wrote:
> Hello.
> I setup some directory and file externs to prune the boost C++ library tree for our projects.
> Like this:
> http://repo/boost/boost_dir/     boost/boost_dir/
> http://repo/boost/boostfile.cpp  boost/boost_file.cpp
> (only a lot more complicated)
> That is, I used directory externals to create the boost/subdirectories from the boost
tree in the working copy, and the file externals to pepper the top-level boost files into
> Worked great in my 1.7.0 client with new working copy format. Told all my co-workers
to "come and get it!" Said co-workers are using various 1.6.x clients, BUT, while they got
the directory externs they got NONE of the file externs. (In the case of 1.6.11 -- I think
-- it complained the top-level boost external was "not a working copy.")
> I guess I want to know WTF? -- since the docs say file externs are supported in 1.6 and
up. Was this sort of nesting broken originally? If so, when was it fixed? Or is it because
I am using the new 1.7 working copy format things are good for me?

I suppose this is one of the (many) problems that was fixed by 1.7's
new working copy format (WC-NG). I suggest that all your users (that
need to work with this nested externals structure) upgrade to 1.7 as
soon as possible.

I quickly searched the issue tracker for issues with the word
"external" in the summary, which were fixed in a 1.7 release [1].
There are 32 such issues :-). Maybe if you go through that list you'll
find the one that causes your problem ... (or it might be yet another
problem with externals that was fixed by wcng, but was not yet known
in the issue tracker).



View raw message