Re: docs/178677: *** [article.html] Error code 1 Stop in /usr/doc.

2013-05-31 Thread Chris Rees
The following reply was made to PR docs/178677; it has been noted by GNATS. From: Chris Rees To: "bug-follo...@freebsd.org" Cc: Subject: Re: docs/178677: *** [article.html] Error code 1 Stop in /usr/doc. Date: Fri, 31 May 2013 17:11:47 +0100 Where did you get the instructions for building th

Re: docs/178049: [handbook] PKGNG information misleading

2013-05-31 Thread crees
Synopsis: [handbook] PKGNG information misleading Responsible-Changed-From-To: freebsd-doc->crees Responsible-Changed-By: crees Responsible-Changed-When: Fri May 31 16:15:47 UTC 2013 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=178049

Re: docs/178818: gmirror(8) says to use rc.early which is no longer available

2013-05-31 Thread Chris Rees
The following reply was made to PR docs/178818; it has been noted by GNATS. From: Chris Rees To: "bug-follo...@freebsd.org" , "freebsd...@freebsd.org" , Pawel Jakub Dawidek Cc: Subject: Re: docs/178818: gmirror(8) says to use rc.early which is no longer available Date: Fri, 31 May 2

Re: Handbook suggestion: Dealing with Moved Ports

2013-05-31 Thread Chris Rees
On 31 May 2013 08:06, Mike Brown wrote: > [ This is a followup to my thread at > http://lists.freebsd.org/pipermail/freebsd-ports/2013-May/083943.html ] > > /usr/ports/UPDATING does not normally mention when ports are moved. Unless > there are special considerations, that info only lives in /usr/

Re: RFC: Upgrading to DocBook 5.0

2013-05-31 Thread Gabor Kovesdan
Em 28-05-2013 23:06, Gabor Kovesdan escreveu: I have a patch to preview how it would look like: http://kovesdan.org/patches/fbsd-docbook5.diff Please comment on this. It is very important to discuss this kind of changes. There are three more changes I would like to do. The maketarget and make

Handbook suggestion: Dealing with Moved Ports

2013-05-31 Thread Mike Brown
[ This is a followup to my thread at http://lists.freebsd.org/pipermail/freebsd-ports/2013-May/083943.html ] /usr/ports/UPDATING does not normally mention when ports are moved. Unless there are special considerations, that info only lives in /usr/ports/MOVED, which isn't really something people