svn commit: r251886 - in head: contrib/apr contrib/apr-util contrib/serf contrib/sqlite3 contrib/subversion share/mk usr.bin usr.bin/svn usr.bin/svn/lib usr.bin/svn/lib/libapr usr.bin/svn/lib/libap...

[Daniel O'Connor]

On 19/06/2013, at 2:18, Andre Oppermann <andre at freebsd.org> wrote:
>> I don't find it unreasonable to ask developers to install the port.
>> And for users it seems all they need is something like portsnap for base.
>> Portsnap already distributes ports svn so it shouldn't be too hard to
>> adapt it for base. And the extra layer it adds is very convenient. Apart
>> from a bigger than usual update maybe, portsnap users never even noticed
>> it was switched from cvs to svn at some point.
> 
> Installing SVN from ports is very painful because of the huge dependency
> chain it carries, with the largest being Python and Perl IIRC.

Perhaps there should be an svnlite port then, or svnstatic or similar.

If an svnstatic port was installed as a package it would have no run time dependencies, so not huge chains of stuff to install.

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C