The handbook on updating/instaling from source shows all commands using 'svn', not 'svnlite'. This is confusing to new users who have no svn. In fact, none of the pages in chapter 23 show svnlite. I think it makes most sense to replace occurrences of the svn command with svnlite, since it's universally available.
The page in question is:
However, the following page:
also mentions that: ``Typically, svn is used to check out the -CURRENT code...''
It should probably also be updated to svnlite. While it does link to the subversion appendix, there is no need for full svn for checkout.
One problem is that the svnlite man pages have never been fixed. They all refer to svn: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191163
svnlite was an import of an external utility into base. I'm hesitant to add more dependencies on it in the docs, since I suspect it still might go away. The right way probably to add a note, like we already have in other places. Each of those has to explain the situation, which only ends up being more confusing. Probably that should all be written in one place so it does not have to be repeated each time. This does not help the new user, because it's a lot of information they don't need. "Use svnlite, which is the same as svn, unless it doesn't exist, in which case install the package. Mentally replace all these example commands with one or the other, whichever one exists."
Barring some active discussion with timeline to remove svnlite (which I'm unaware of), what you're suggesting is to leave the handbook in an inconsistent state. Recalling how long the cvs->svn move took, maybe holding our breath waiting for svnlite to go away isn't recommended. The handbook is really the one place new users are urged to read prior to any discussion on mailing lists, newsgroups, irc, etc. Granted there is an issue with base system documentation that 194910 attempts to address. That bug was filed nearly 3 years ago. system.
Referencing 191163: a patch to update svnlite documentation makes a lot of sense! Is there anything stopping that, or is it just on the giant 'nobody's submitted a patch for this yet' list?
I'll look into it.