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...

[David Chisnall]

On 19 Jun 2013, at 16:13, John Baldwin <jhb at FreeBSD.org> wrote:

> portsnap does not work for src.  (I thought we had already covered that
> in earlier threads?)  portsnap only moves forward.  It is a very important
> feature for our users that whatever tool they use for source updating be
> bidirectional.  In particular it is very common practice to use a bisect
> operation to isolate changes responsible for regressions.

Freebsd-update can manage the src tree.  I'm not entirely clear on what use-case we are addressing here.  Is it:

- FreeBSD developers, who are probably okay with installing a port, but would prefer a version that didn't depend on kitchen/sink?

- Users, who wish to be able to update the source tree and then either build world, or build some optional parts that are not part of the default install?

- Some other category of svn consumer?

I think having a definitive statement as to the intention of svnlite would help frame the discussion in a more productive format.

David