From owner-freebsd-questions@freebsd.org Mon May 22 05:11:01 2017 Return-Path: Delivered-To: freebsd-questions@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 C5FACD77066; Mon, 22 May 2017 05:11:01 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu [18.9.25.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 42AA91520; Mon, 22 May 2017 05:11:00 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190d-e73ff7000000547f-81-592271aec2cd Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id F5.DB.21631.EA172295; Mon, 22 May 2017 01:05:50 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id v4M55n39024982; Mon, 22 May 2017 01:05:49 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v4M55ihC025472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 22 May 2017 01:05:47 -0400 Date: Mon, 22 May 2017 00:05:44 -0500 From: Benjamin Kaduk To: Ernie Luzar Cc: FreeBSD questions , "freebsd-doc@freebsd.org" Subject: Re: having trouble making changes to the handbook Message-ID: <20170522050544.GS39245@kduck.kaduk.org> References: <592041FB.9030408@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <592041FB.9030408@gmail.com> User-Agent: Mutt/1.7.1 (2016-10-04) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrAIsWRmVeSWpSXmKPExsUixG6nrruuUCnS4P09U4tTZ7pYLV5+3cRi cf30JHYHZo8Zn+azeOycdZc9gCmKyyYlNSezLLVI3y6BK+PM5+eMBe2SFd+PrGZuYGwX6WLk 5JAQMJFYtvgRSxcjF4eQwGImif7XvUwQzkZGiavvmlghnKtMEpvvzGcEaWERUJX4ua+VGcRm E1CRaOi+DGaLANmbtzxlA7GZBYolXjR+YgKxhQWsJF5dWQlWwwu0bvfXeWBxIQENiYfzTrBD xAUlTs58wgLRqyVx499LoBoOIFtaYvk/DpAwp4CmxLlZ98HGiAooS/w9fI9lAqPALCTds5B0 z0LoXsDIvIpRNiW3Sjc3MTOnODVZtzg5MS8vtUjXSC83s0QvNaV0EyMoYDkleXcw/rvrdYhR gINRiYf3xA/FSCHWxLLiytxDjJIcTEqivBudlCKF+JLyUyozEosz4otKc1KLDzFKcDArifDu +wZUzpuSWFmVWpQPk5LmYFES5xXXaIwQEkhPLEnNTk0tSC2CycpwcChJ8PIVAA0VLEpNT61I y8wpQUgzcXCCDOcBGm4IUsNbXJCYW5yZDpE/xagoJc6blA+UEABJZJTmwfWCEopE9v6aV4zi QK8I8y4HaecBJiO47ldAg5mABls/kwcZXJKIkJJqYAzzSjJIP6aednJzzcz915bFTdOxcV1x zZ6j4ZR/mcXLvwv6mY6tNlj2/pCEk+22fUfNRGs3TC5w//ErWTe6KOOJsL3fpGsxTh35gmdm lvr5aPuJ3/3LILbOOpX74ATb4xG1r8t37/czTAuyV3J+8+za8xKevpXLPV+kbD4tp5H/pVx8 kZufjxJLcUaioRZzUXEiALYh8K4DAwAA X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2017 05:11:01 -0000 On Sat, May 20, 2017 at 09:17:47AM -0400, Ernie Luzar wrote: > I am following the info in this link > https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/ > > I installed the textproc/docproj package. > > The above link says that svn is installed as part of that port. But it > really is not. Have to use the built in svnlite command. It seems that https://svnweb.freebsd.org/ports/head/textproc/docproj/Makefile?revision=420130&view=markup has some logic to not depend on devel/subversion when /usr/bin/svnlite is present in the build environment, which is arguably not the best choice, since the build environment need not match the install environment when pre-built packages are in use. > The shown command > "svnlite checkout https://svn.FreeBSD.org/doc/head ~/doc" > downloads far more items than wanted. This needs better example of just > downloading the desired language version of the handbook plus any > "shared directories" required for "make command" to work. How do I do this? It is intentionally undocumented, as there are multiple parts from the root needed to build a translation tree (in addition to the english sources, which are used when translations do not exist). No one has gone through to enumrate the list and commit to keeping it up to date as the build system changes. That is to say, you are free to attempt it, but it will require some investigation and it will probably be simpler overall to just accept the extra bytes as the cost of convenience. > I ran the "igor -R filename.xml | less -RS" command on the chapter I > wanted to work on before making any changes. To my surprise a bunch of > error are shown. Since these error are all already in the handbook > source I see no reason why I should try to correct them. Just because errors are preexisting they should be ignored instead of fixed? To be clear, no one is going to insist that you fix all issues in a file before adding content to it, but it is also a fine idea to make an initial cleanup patch before starting to do further work. As to how this situation might arise, the existing content is often quite old, and igore is a comparatively new tool (and continues to receive updates), so it is not surprising that there is old content that does not fully comply to the current standards. > When I ran the "make" command the resulting html files are just written > into the directory that "make" was run from. How do I tell "make" to > write the output to a location of my selection? 'make install' should respect DESTDIR, of course, and I think (but did not test) that the usual OBJDIR-manipulation variables would work. > What is really lacking is a way to view the changed output in a command > line browser. Installing a desktop just to view the changed handbook is > not an acceptable solution. But, what would the other location of your selection be that would be differently viewable in a command-line browser than the html files in the build tree? I generally use a browser (desktop or not) to view the html files next to the xml sources, which is usually "good enough" for what I need to do. -Ben