From owner-freebsd-ports@freebsd.org Wed Dec 27 10:53:01 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A27FE84F43 for ; Wed, 27 Dec 2017 10:53:01 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-cmomta03.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 78E4019F4 for ; Wed, 27 Dec 2017 10:53:00 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from localhost ([74.134.208.22]) by cmsmtp with ESMTP id U9Hze09LS1nXhU9I1edE3c; Wed, 27 Dec 2017 10:50:26 +0000 Date: Wed, 27 Dec 2017 10:50:11 +0000 From: "Thomas Mueller" To: freebsd-ports@freebsd.org Subject: Re: How do I recover a lost ports directory with svn? References: <20171226162754.GE99670@rancor.immure.com> <44bmilcm0f.fsf@lowell-desk.lan> <20171226194710.GG99670@rancor.immure.com> <44373wdi5p.fsf@lowell-desk.lan> X-CMAE-Envelope: MS4wfKGzxx/jF2v9p+EoOxTiK1uSVKnL+Hw3yTXhEffVdMRCJOzyDQkAk5e0P9kMfBR1hpO37LFMHvSSFxFzdaXVvICP97LD5Q2b103AX670n6Hd/PkoW9m0 q92OfNRkYPD7mPW4VIVA/bWsPDgN6JLX/qBxxhz1vD79GTBpdtjI+WJl X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2017 10:53:01 -0000 from Lowell Gilbert: > That's fair. The help messages are enough for me to work out syntax > without going back to first principles, but, yes, that's pretty much > what I expect from a man page. > > Personally, I would much prefer a real man page. > Funny you should mention that. Some years back, I bashed out a script > that turned the svn help into a browsable document. I can't find that > tool in a quick search of my backups, and I don't even remember whether > it converted things into HTML or info files. [As an emacs user, info is > roughly equivalent to HTML for such things; I have no idea how info can > be useful if you aren't using emacs to browse the docs.] > But the point is that I found the cross-link information fairly easy to > parse. And once you can do that, you can turn it into anything useful. I wish GNU would switch away from info in favor of man or html! When I ran Linux Slackware 13.0, Konqueror in KDE had a good info viewer. Otherwise, there is misc/pinfo in ports. Tom