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

Re: Installation [was Re: transaction roots]

From: Daniel Stenberg <daniel_at_haxx.se>
Date: 2001-03-30 10:17:03 CEST

On Fri, 30 Mar 2001, Tripp Lilley wrote:

> > 1 - we're not always system administrators when we want to run SVN on a few
> > simple files. requiring apache is an immense barrier in that scenario.
>
> I hate to be cavalier, but this is what I envision:
>
> rpm -i svn-toto-1.0-1.i386.rpm

Now, I'm not any RPM knowledgable person, but doesn't that use hard-coded
paths? If you're not sysadmin, how can to install files in system
directories?

> > What about the "weekend warrior" who uses a machine he can't install
> > servers on?
>
> A relocatable version of the above kit, installed in the user's home
> directory, listening on an unprivileged port (probably computed based on
> an offset and the user's UID, so it doesn't conflict with another user
> also evaluating SVN).

You're missing my point (my fault, I didn't really spell it out).

I'm not talking about a fysical limitation, I'm talking system policies. Like
imagine my account over at my web hotel that hosts a bazillion domains and
users. They frawn upon servers started by users. Sure, finding a
non-priveledged port is simple enough, but that's not the problem I'd have to
work-around here.

Any program that requires a server is out of the question for me to install
there, unless I can get the management's attention and have their permission
or perhaps have them do the job to set it up system-wide.

I don't know how common this scenario is, but I know for sure that I've had
access to many such machines during my days that have imposed similar limits.

> I guess I just feel like the entire "local" versus "remote" access
> dichotomy is "askin' fer trouble". It duplicates code, even when you're
> diligent about sharing code.

Well, any new feature adds code and thus also problems/bugs. I think of
local-mode as a feature. A cool feature actually.

> It adds new places for bugs to hide. It allows users and sysadmins to do
> grievous damage if they're not aware of the distinction

How would that be? How would I cause "grievous damage" to my local repository
if I mistakenly think it is a "remote" one all of a sudden?

-- 
      Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
   ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
Received on Sat Oct 21 14:36:26 2006

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