Thanks for the pointers, Konstantin. I've promoted the bug to
1.8-consider. (It's not a release blocker.)
Konstantin Kolinko wrote on Tue, Apr 17, 2012 at 03:02:23 +0400:
> 2012/4/16 Daniel Shahaf <danielsh_at_elego.de>:
> > Kuno Meyer wrote on Mon, Apr 16, 2012 at 16:51:29 +0200:
> >> Daniel Shahaf wrote on Mon, 16 Apr 2012 14:48:45 +0300:
> >> > Kuno Meyer wrote on Mon, Apr 16, 2012 at 10:31:33 +0000:
> >> > > Is it by design that 'svn cleanup' ignores externals and that there is
> >> > no way to
> >> > > include them?
> >> > >
> >> >
> >> > You should be able to include them by naming them explicitly:
> >> >
> >> > % svn cleanup path/to/external/dir
> >> Thanks. This is what I did.
> >> However, since I am not the one who set up the "externals" layout of our source code repository, it took me some time to understand the way a working copy containing external references is organized.
> >> And then again, I realized that my custom update and rebuild script fails at garbage collecting unreferenced pristines in sub-WCs included by "externals" defnitions. But that's another story...
> > That's a good point actually, since presently 'svn cleanup' is required
> > to garbage-collect pristines, having it recurse to externals
> > automatically makes even more sense.
> > Has anyone filed a bug report about this yet? If not I will..
> > (so it's not forgotten, etc)
> There is
> Maybe update its target milestone to be 1.8?
> Here is previous discussion, 6 months ago (dev@, 2011-10):
> For reference, current thread:
> Best regards,
> Konstantin Kolinko
Received on 2012-04-17 08:33:39 CEST