Date: Wed, 27 Mar 2002 13:37:46 +0200 From: "Patrick O'Reilly" <bsd@perimeter.co.za> To: "FreeBSD Question List" <freebsd-questions@FreeBSD.ORG> Cc: "Giorgos Keramidas" <keramida@ceid.upatras.gr>, "Mike Meyer" <mwm-dated-1017512731.7e461a@mired.org> Subject: Re: CVSUP doc-all - now what? [solved - part 2] Message-ID: <000e01c1d583$d4cc37b0$b50d030a@patrick>
next in thread | raw e-mail | index | archive | help
> From: "Patrick O'Reilly" <peri@perimeter.co.za> > > Ok, thanks to Giorgos and Mike for your pointers! > > I followed these steps (given by Giorgos): > 1. Install the textproc/docproj port: > # cd /usr/ports/textproc/docproj > # make install JADETEX=no > > 2. Enter /usr/doc and run `make'. > # cd /usr/doc > # make > > 3. Install the documentation to /usr/share/doc. > # cd /usr/doc > # make install > > It worked perfectly. > > I will be testing Mike's suggestion (make update), and post another > follow up later. > > I was a little surprised at how many other ports came along for the ride > with the textproc/docproj port. The dependencies included about 30 > other ports (as reported by "portupgrade -nR docproj")! Anyway, one day > I might even try to help on the 'docproj' myself, so the extra goodies > will be required :) > Right, as promised, here is the summary following further testing of the suggestions from Mike and Giorgos: 1) Installing the Docproj Port, and making documentation. Steps 1 to 3 above covered that, and highlighted my surprise at the number of ports bundled with docproj. As Giorgos has pointed out, this solution was overkill for my needs (I really just wanted a local mirror of the latest documentation), but in hindsight I am glad to have this as the docproj is one area in which I may be able to contribute to the FreeBSD project in the future. 2) Using 'make update' in place of cvsup. I decided to go the whole hog, and configured my box to update src, doc and ports all from the /usr/src Makefile. How? I added the following to /etc/make.conf: ------------------- SUP_UPDATE=true SUP=/usr/local/bin/cvsup SUP_FLAGS=" -L 2 " SUPFILE=/peri/cvsup/cvsup_src-all_STABLE PORTSSUPFILE=/peri/cvsup/cvsup_ports-all DOCSUPFILE=/peri/cvsup/cvsup_doc-all DOC_LANG=en_US.ISO8859-1 ------------------- Note that the files referenced for the three SUPFILE values were the CVS sup files that I had previously used manually in commands like "cvsup -L 2 /peri/cvsup/cvsup_src-all_STABLE". Looking at the above values in make.conf it is easy to see how make reproduces the cvsup command from these values. The beauty of this is that now I just do: ------------------- # cd /usr/src # make update ------------------- and it will run cvsup on all the collections, one after the other. 3) Installing the updates. I have successfully applied all the updates received via 'make update' by using the exact same procedures I used whenever I did manual cvsup before. ie: after the 'make update', I did (briefly) the following: a) to build my world :- # cd /usr/src # make buildworld # make buildkernel # make installkernel ( boot -s and mount up the disks ) # make installworld # mergemaster -i ( boot ) b) to upgrade any ports :- # cd /usr/ports # portupgrade -rRa (OK, I am not that brave, but you get what I mean) c) to install the latest documentation (as Giorgos said before) :- # cd /usr/doc # make # make install There you have it. Thanks again to the folks who helped me, and I hope that this little reference to what I did is of use to someone else who might be wanting to do the same, or similar. Regards, Patrick O'Reilly. --- Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000e01c1d583$d4cc37b0$b50d030a>