Date: Mon, 15 Oct 2012 12:04:58 -0400 (EDT) From: Darrel <levitch@iglou.com> To: Matthew Seaman <matthew@FreeBSD.org> Cc: questions@freebsd.org Subject: [solved]: local-distfiles | blackend Message-ID: <alpine.GSO.2.00.1210151145060.12544@shell1> In-Reply-To: <507BA786.6050300@FreeBSD.org> References: <alpine.GSO.2.00.1210141735510.23423@shell1> <507BA786.6050300@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--- >> >> svn co svn://svn.freebsd.org/doc/release/9.1.0/en_US.ISO8859-1/ >> --- >> >> Does this method of having a local copy of docs around seem alright, >> or does someone know that there is a better way? > > That should work fine, if what you are after are the .xml source files > the documentation is compiled from. Note that compiling all this stuff > into HTML or PDF requires a moderately large toolchain to be installed. > (see: textproc/docproj* in ports.) > > Also, the URL doc/release/9.1.0/en_US.ISO8859-1 -- that's a tag in SVN, > meaning it is never going to be updated. Check out HEAD if you want to > be able to track changes. > > You always used to be able to install a pre-compiled doc bundle from the > install media. What with changes over the last several months I don't > know if that is still possible, but if it is, then that would probably > be more suitable if all you want is to have a reference copy of the docs > to hand. Thank you, Matthew. It seems like what I had planned to do would have involved inventing the wheel. I recall seeing a docs option in the media as well. There is something in ports which will be fine for my purposes- I can get html and plain text. There are also knobs for postscript and portable documents for those interested. $ ls /usr/ports/misc/ | grep freebsd-doc Darrel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.2.00.1210151145060.12544>