Greg Stein <firstname.lastname@example.org> writes:
> httpd-2.0, apr, and apr-util to name a few. However, in SVN land, I believe
> we're have a separate SVN repository for each project. I think the projects
I have seen this stated a few other places, but i don't understand
it. I am currently managing multiple projects in one repository,
the same way i did in CVS. It works quite well, and i'm sure there
are advantages i haven't thought of to having them share the same
database back-end (i imagine this will become even more valuable
when a SQL back-end becomes available).
I don't want to deal with separate repositories, and i probably
won't be the only one. What makes you think this behavior opposite
to that of CVS users will become common?
> As a result, cross-repository "modules" are quite important for SVN. It also
> means that when the ASF switches over to SVN, we can set up a "module" for
> Subversion that references the ASF SVN repositories.
I don't think cross-repository modules will be as important as you
think, but if i am wrong there is still a better way to handle it
than text files. If we think of the link behavior i previously
proposed as a hard link, we can think of a symbolic link as a sort
of link the client *does* have to concern itself with.
That is, a link appears identical to a file or directory and the
client goes about its business. Just as hard links are confined
to a single physical filesystem in Unix, this link is confined to
a single repository. A symbolic link, on the other hand, can point
to an external resource. So the client sees that you are committing
to two files, one here in this directory for repository A, and
another here in this symlink for repository B. It sends the changes
to the appropriate repository/server.
Unless there is something i'm missing and there's a good reason
why different projects should not share the same repository, i
won't have much interest in the symbolic link functionality, so i
would provide the original functionality i proposed first. Then,
time permitting, i might work on this second type of link.
Eric Gillespie <*> email@example.com
Conformity is a sin.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu May 2 01:53:02 2002