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

Using the client API with an unusual filesystem

From: Tom Potts <karaken12_at_gmail.com>
Date: Tue, 21 Apr 2009 23:09:29 +0100

Hi, all. I've got a bit of a complicated problem, and not much of an idea
where to get started, so please bear with me if this is a bit vague.

The situation I have is a software project which maintains its own indexed
system (effectively a filesystem, though it appears as a directory with some
files inside). What I want to do is be able to add individual items within
these indexed systems to a Subversion repository, as if they were regular
files. The way I envisioned this working was with a custom Subversion
client that could read the indexed systems natively, and then use the
standard API.

Alternatively, if I could 'fool' the standard client into thinking that the
indexed systems were (in some way) regular directories with regular files in
them, that would work too, with the caveat that the .svn directory should
really go somewhere else.

The trouble with both these approaches is that I don't really know where to
start. I've taken a look at chapter 8 in the Book, and I've downloaded and
compiled the minimal_client example, so I think I'm happy with how to write
my own client. The bit I don't know about is how to get the API to read and
write the 'files' through my own routines, rather than natively through the
OS.

If anyone has any thoughts on this, no matter how vague or seemingly
off-topic, please reply -- I really need a jumping-off point to get going
with. :o)

Thanks,
Tom Potts

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1849358

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-22 00:11:49 CEST

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

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