Fair enough.
Adding the external to the intermediate folder is not an option
unfortunately, our QA dept likes to have all externals defined at the
root so they can be easily reviewed, modified, pinned to certain
revisions etc.
I thought maybe subclipse could do an extra svn status on any subdirs
that appeared unversioned or something. Not very nice and I agree that
it is something that should be handled better by svn itself. Should I
enter a feature request on SVN?
Mark Phippard wrote:
> On 10/29/07, Tom Walter <tom.walter@hitwise.com> wrote:
>
>> If I have an external definition that outputs to a directory deeper than
>> the one that the external is defined on eg.
>>
>> current_dir/subdir http://svn/trunk/myexternal
>>
>> Then the /subdir folder is shown in subclipse as unversioned, and
>> appears in commit dialogs as unversioned also. With a large number of
>> externals, this can make the commit dialog noisy when you have to go
>> through and determine which items are actually unversioned and which
>> aren't every time. It also makes the 'compute deep outgoing state' less
>> useful since a lot of folders will show up as having changes when in
>> fact they are externals.
>>
>> I've mentioned this on the user group before so I understand that the
>> issue is really that 'svn status' sees these deep externals as
>> unversioned also, but subclipse does other tweaks to get around
>> difficulties in svn commands, and this seems like a handy one to me.
>>
>
> There is no Subversion command or API that tells us that the folder is
> anything other than unversioned. Absent such API, I do not see how it
> would be possible to know that this is an externals folder.
>
> Why not just add the intermediate folder to the main repository and
> add the svn:externals property to it?
>
>
>
Received on Tue Oct 30 01:51:24 2007