Thanks for your quick and detailed response! >> I noticed recently that the behavior when working with externals have >> changed in SVN 1.7. Local changes to the svn:externals property in the >> working copy is by default not honored during an update, before a commit. > There are fundamental problems with how we have to process the svn:externals > property: we need the version *exactly* how it was at the last svn update > and the 'latest' version, to make the svn:externals processing handle > definition changes. > (We really need the *CHANGES of externals*...) ... > But the real solution is to add a store which contains what externals we > knew at the last update.
Ah. We need the pristine versions of the properties. But they must be known already, or reverts of property changes would not work. What am I missing here? > And I'm working on that right now. Once that store is operational (guess: by > the end of this week), we can safely re-enable local changes to > svn:externals, but without the problems of the past. Oh! That's great! Good to know that someone is looking into this. When you are writing "store", I guess you are referring to something other than the wc database. If that is so, what is the reason not to put it in the database? Hans-Emil
