--On September 1, 2005 9:19:25 AM -0400 David James <james82@gmail.com> wrote:
> It may be a one-time inconvenience to install dependencies, but it's a
> large inconvenience if you work with a system that does not have
> binary packages for the Subversion dependencies. On the systems I work
> with, I am not a root user, so I am unable to install binary packages.
I'll point out that University machines (on which I also bootstrap) never
allow students to build or install packages - and they don't allow any
dependencies to be installed anywhere. On those machines, I build svn into my
home dir.
> Because Subversion releases ship with many of its dependencies,
> Subversion is refreshingly easy to install.
+1.
> I don't think would be a good idea to just "stop shipping
> dependencies". Why get rid of a great feature, that makes Subversion
> much easier to configure and install, just so that we can have a
> smaller download?
>
> We can accomplish the same goal without causing users pain by
> splitting Subversion into two packages:
> 1. Subversion Core
> 2. Subversion Dependencies
> - apr
> - apr-util
> - neon
>
> If you want a quick download, you can just download the Subversion
> Core. If you find out you're missing dependencies, you can download
> the "Subversion Dependencies" package. Either way, you'll never have
> to complete more than two steps to install a Subversion release.
I would personally prefer having two tarballs: one with just the core and one
with the core and all of the dependencies. *shrug* -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 1 18:24:45 2005