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

Re: svn externals: 2 paths for authentication, but only one external?

From: John Owens <john_owens_at_yahoo.com>
Date: Fri, 17 Apr 2009 19:35:14 +0000 (UTC)

Andrey Repin <anrdaemon <at> freemail.ru> writes:

> Actually, both.
> I can't imagine any sane way to change links depends on the auth scheme(!)
> used, and I can't imagine situation, in which it could be need.
> Also, please explain, how would you resolve conflicts when users commit their
> changes?

OK, let me explain the actual situation in more detail. I am happy
to hear about a different way to solve it!

I am on a campus that has Kerberos authentication for people on the
campus. This is preferred. I have an svn path so my colleagues on
campus can use svn using Kerberos authentication. It's also better to
do this since I don't have to set up password authentication.

However, some of my colleagues are NOT on campus. For them I have a
different authentication path. It uses hashed passwords. It's not as
secure or good as Kerberos, so I avoid using it if possible. But it
is the only way off-campus people can use our repository.

Now, we write papers together, and those papers are stored in svn. So
we have a /papers directory in the repository. We also have a bibliography
file that is shared among all papers in /bib/all.bib.

What I really want is to have all.bib included in each paper
(/papers/paper/all.bib). A softlink would work great, but svn doesn't
support softlinks. But externals is fine - I can add bib in each paper
directory as an external and it fetches nicely. Then my users only
have to fetch the one paper directory and nothing else, which is

The problem is that when I add bib as an external, I have to add it under
one of the two authentication paths, either Kerberos or password. If
I pick one, the external doesn't work for the other one. That's the
problem I'm trying to solve.

Happy to hear suggestions and/or ideas for how I could structure this
in a different way to accomplish my goal of two authentication schemes
where users in either scheme can do one "svn co" to get both the paper
and the bib.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-17 21:36:32 CEST

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