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

availability of svn_wc_entry->repos

From: Daniel Rall <dlr_at_finemaltcoding.com>
Date: 2005-09-27 01:36:55 CEST

John wrote:
> Daniel L. Rall wrote:
> > On Fri, 23 Sep 2005, Peter N. Lundblad wrote:
> >>Wrong, svn_wc_entry->repos is populated when the info is in the entries
> >>file, which it will be after an update with an 1.3 client, so you can add
> >>that whenever you want to. (But bear in mind that it might be null).
> >
> >
> > ...as illustrated by r16145. See r16141 for how to use that info.
> But it appears that only the repos_root entry for the _directory_ is
> populated, not for the _files_ contained in that directory.

This is consistent with the data I'm seeing in WC .svn/entries files.
(There's no reason to duplicate this piece of data.)

> Consequently, I cannot create a $ReposPath$ keyword until
> there is a way to grab one of the entry values from the directory
> given only the file. Or am I missing something?

That's my understanding, yes. svn_wc_copy2() opens the existing
.svn/entries administrative file, and then gets the svn_wc_entry for the
directory being operated upon:

  SVN_ERR (svn_wc_adm_probe_open3 (&adm_access, NULL, src_path, FALSE, -1,
                                   cancel_func, cancel_baton, pool));
  SVN_ERR (svn_wc_entry (&src_entry, svn_wc_adm_access_path (adm_access),
                         adm_access, FALSE, pool));

Erik Hülsmann pointed out that it would be nice if files inherited the repos
setting of their parent directory. I have not confirmed whether this is
occuring for this case in the source code (though take_from_entry() and
svn_wc__atts_to_entry() in libsvn_wc/entries.c look promising).

- Dan

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 27 01:36:20 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.