[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Ev2 symlinks

From: Daniel Shahaf <danielsh_at_elego.de>
Date: Fri, 28 Jun 2013 08:59:49 +0300

Greg Stein wrote on Fri, Jun 28, 2013 at 01:25:42 -0400:
> On Fri, Jun 28, 2013 at 1:19 AM, Daniel Shahaf <danielsh_at_elego.de> wrote:
> >...
> > So, to be explicit: calling add_symlink() when driving the FS commit
> > editor is a bug;
> Of course not. The FS commit editor knows how to represent a symlink
> within the FS. (however the FS design changes over time)

Okay. Suppose Ev2 is released in 1.9 and svn:special=blockdev in 1.10.
An app is built against libsvn_fs-1.9 and ran with libsvn_fs-1.10. The
app calls svn_editor_add_file(svn:special='*', contents="blockdev ...").
At what point does this call get converted to svn_editor_add_blockdev()?

You want to allow written-against-1.9 clients to call add_file() that
way, but you just said below that that add_file() call is forbidden to
written-against-1.10 clients. How do these requirements coexist?

> > calling add_file(svn:special='*', contents="link foo")
> > when driving the wc-ng update editor is also a bug.
> Correct. If you're driving Ev2, then you should not be working with
> "special" files. You should be working with the appropriate node_kind
> values.
> The "old" "special" representation is just that: old. In wc-ng and
> Ev2, you work directly with symlinks.
> >...
> Cheers,
> -g
Received on 2013-06-28 08:00:42 CEST

This is an archived mail posted to the Subversion Dev mailing list.