Date: Sat, 15 May 1999 19:07:12 +0200 From: Wolfram Schneider <wosch@panke.de.freebsd.org> To: nclayton@lehman.com, Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG> Cc: doc@FreeBSD.ORG Subject: Re: Can't build handbook Message-ID: <19990515190712.02032@panke.de.freebsd.org> In-Reply-To: <19990513124039.N14492@lehman.com>; from nclayton@lehman.com on Thu, May 13, 1999 at 12:40:39PM %2B0100 References: <19990508141141.A20366@holly.dyndns.org> <XFMail.990508212539.jesusr@ncsa.es> <19990508231333.45191@panke.de.freebsd.org> <19990510111306.I14492@lehman.com> <199905110749.AAA28713@silvia.hip.berkeley.edu> <19990513130423.49638@panke.de.freebsd.org> <19990513124039.N14492@lehman.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1999-05-13 12:40:39 +0100, nclayton@lehman.com wrote: > Yes, if they check it out anywhere other than /usr/doc they will need > to set DOC_PREFIX. As I've already explained, this is a hack that will > (eventually) go away. In the meantime we can do one of two things; Some weeks ago it was possible to checkout the handbook and compile it: $ cvs co handbook; cd handbook; make No it is no longer possible. You have to checkout either the whole doc tree or know exactly which sub-directories you need: $ cvs co doc/en/handbook doc/sgml doc/share doc/en/share $ cd doc/en/handbook; make and set the DOC_PREFIX variable to $PWD/doc. I'm not surprised that we are getting complaints and the documentation pages are more often broken ;-( > 1. Keep the "DOC_PREFIX?=/usr/doc" line in docproj.docbook.mk, but > change the path from /usr/doc to something else. > > I think changing the path is a bad idea, as anyone who's just > cut-n-pasted the CVSup configurations is going to be inconvenienced. > > 2. Stick in some code that checks for an empty DOC_PREFIX, and advises > the user on how to fix it. Or better yet, looks in DOC_PREFIX > first the make sure the appropriate files are there, and warns the > user if they aren't. > > I posted code that does this earlier on in this thread. > > I think option 2 is the best way to go. We can keep /usr/doc as the > default, and it will work if the user has been storing a checked out > copy in /usr/doc. If they haven't then the DOC_PREFIX test will discover > that, abort the build, and print instructions about what they should do. I prefer option 2). -- Wolfram Schneider <wosch@freebsd.org> http://wolfram.schneider.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990515190712.02032>