Joachim Kathmann wrote:
[snip]
> I'm quite astonished that everybody seems to accept TortoiseSVN
> without this feature. There HAS to be a possibility to browse for a
> project folder from within TortoiseSVN without knowing its exact path
> on the server or opening a network share or building an index by
> script.
Really? There has to be?
I guess all the users of TSVN must be completely insane then if they're
using it even if it doesn't have that feature!
> My idea of implementing it, is to define the svn folder in
> Tortoise as svn root (I do not mean root of a repository, but root
> for all repositories) and then list it's contents without using
> WebDAV as an exception. On opening a subfolder (repository) in the
> tree, it's contents is shown using WebDAV as you're doing it now.
> Where's the problem to do that?
The problem is that TSVN would have to implement a whole new protocol to
do that. And if we do that for http, then people will want the same for
https, svn, svn+ssh, ...
Then we would have to implement some access control, because then people
will want to prevent users from even seeing some of those repositories.
And what's the point? I mean you still would have to give the users the
URL to the "root" and they would have to enter that somewhere.
>> The only way you can get close to what you want is putting an
>> index.html file in the svn folder. That index.html then contains
>> links to all your projects. AFAIK some people already wrote scripts
>> which build such an index.html file by listing the repositories
>> (berkeley db folders). Search the subversion mailing list for those
>> - or just ask on the list there.
>
>
> Don't you think that's a bit inconvenient? I mean, what do I need a
> GUI for if I have to write a server script for finding my projects in
> the first place.
The GUI is a _client_, not a server. Servers don't have a GUI - they
need the resources for serving not for graphics.
> Sorry for the full quote, but I thought it'll be better to keep the
Please don't do that! It makes a mail very hard to read.
[snip a lot]
>> If you decide to have a separate repository for each project, then
>> do the following: - under d:\svn create a new folder for each
>> project - then, inside d:\svn\project1 use the TSVN command "create
>> repository here" - point the SVNParentPath to d:\svn now you can
>> access the project by pointing to http://server/svn/project1
>
> That's exacly what we did before adding user access rights and trying
> to browse for projects.
If you did that, then you _can_ browse your projects!
>> - use the autz_svn module to provide access on a per directory
>> basis
>
> Does that work in combination with SSPI? How?
Sure. Just read the TSVN docs on our website or in the help file which
comes with TSVN. There's a whole chapter on how to set up a server and a
section about how to set up SSPI authentication.
>> If you decide to have one repository for each project, then do the
>> following: - inside d:\svn use the TSVN command "create repository
>> here" - point SVNPath to d:\svn (_not_ SVNParentPath) - you can now
>> access the repository by pointing to http://server/svn/ - use the
>> repository browser to create a directory structure inside the
>> repository, e.g. trunk/project1 branches/project1 tags/project1
>
> We tried that but did it wrong. We created folders
> trunk/branches/tags inside svn/ and then created repositories for
> Proj1,Proj2 within these subfolders. Maybe that's the solution,
> creating the repository directy in SVN before adding trunk, etc. But
> on the other hand, wouldn't that mean all projects share revision
> numbers which I would personally regard as awfully confusing.
Yes, if all projects are in the same repository, then those projects
share the revisions numbers.
[snip]
> We hope not to steal too much of your precious time as a developer,
> but see, we're just stuck and without solving the problems mentioned
> we can't use Subversion and TortoiseSVN as a fully satisfying
> replacement for VSS.
To avoid that in the future, please, please follow the rules here:
- write your mails in a kindly manner. We don't like it if you're
complaining and whining about a program we spend many, many hours
working on for free. You don't pay us so you're not allowed to talk bad
about us or the program, and you're not allowed to demand features - you
can ask nicely for them.
- don't quote whole mails. It's a real mess to read such mails - and
you're wasting valuable electrons.
- never, ever mail the developers directly! If you think your mail isn't
suited for the mailing list then don't send it at all. If you send the
mail to single persons, then they're forced to answer you (or if you
keep doing it just delete your mails!), but if you send them to the
mailing list anyone who's got the answer and a little time left can answer.
- if you're not subscribed to the list, then ask for people to cc you.
- read http://tortoisesvn.tigris.org/list_etiquette.html
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Jul 14 22:19:57 2004