On 8/2/06, Christopher Taylor <chtaylo3@gmail.com> wrote:
> Dear List,
>
> I'm looking through the code of libsvn_fs and I'm wondering how far
> down do I need to go in order for my program to me able to change
> properties of a file at a previous revision.
>
> I'm trying to do this because I want to compute some statistics on
> files stored in a repository. The statistics are somewhat time
> consuming to compute and as such I will not be able to be done in
> near-realtime ... I'll need to compute them after the commit has
> happened.
>
> Specifically I'm looking at svn_fs_change_node_prop right now but it
> seems to need a transaction root (which I will not have) so I think I
> need to go lower. Any ideas?
>
> I realize that what I'm trying to accomplish defeats the purpose of
> versioned properties, but I can't very well justify creating a new
> version of a file just to attach some statistics. These statistics
> are about a specific version of the baseline, and as such need to be
> properly alligned to that revision. Even if I could justify doing a
> whole new revision just to record the statistics, I can't gaurentee
> that the calculations will be done before the next commit. That being
> said, such statistics will probably only be computed for tags.
>
> I could hold such statistics outside SVN, but it would be soooo much
> cleaner if I didn't have to do that.
You cannot change properties on items in previous revisions, you have
to commit new versions to change a revision. This is rather central
to how Subversion's repository works, old data is read-only and cannot
be changed. Doing so would break many things, including existing
working copies.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 2 22:58:08 2006