David Glasser wrote:
> On Fri, Jun 6, 2008 at 8:20 AM, Blair Zajac <blair_at_orcaware.com> wrote:
>> I'm working on getting intra-repository file externals into svn's wc, as an
>> addition to our support for directory externals.
>>
>> A couple of design questions, but first a design point. I'm implementing
>> file externals using the existing support in 1.5 that you can do 'touch foo;
>> svn add foo; svn switch foo URL'. So under the hood, having a file external
>> sets up a switched file. The existence of some additional fields in the
>> entries will tell the client that it still needs to be treated specially.
>
> I haven't completely thought through exactly what you're saying, but
> anything that makes "externals" more like "repository-defined
> suggestions for switches" is great in my book.
>
>> Because the svn:externals property can add an external to subdirectories and
>> users may do updates from a subdirectory, svn may not know that a switched
>> path is a file external, so I need to add a marker in the wc entries that
>> something is a file external and not just a switched path.
>>
>> So I can add a single entry line into .svn/entries with a single line,
>> either of the two following form:
>>
>> [HEAD|r\d+] URL
>>
>> or two separate lines:
>>
>> URL
>> [HEAD|r\d+]
>>
>> The two have to both be there for this to work, so maybe the first?
Yes, I'm going to switch to that.
> Parsing sucks. Later we'll decide that you can support, say, the
> {DATE} revision type, which can have a space in it. Be less
> ambiguous.
I'm not going to have {DATE} in this line. The svn:externals property may only
have r\d+ and even if we allowed {DATE} in the svn:externals, I would still
resolve this to a revision for the .svn/entries file.
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-09 17:24:31 CEST