From owner-freebsd-www Sat Mar 29 20:06:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA04602 for www-outgoing; Sat, 29 Mar 1997 20:06:14 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA04588 for ; Sat, 29 Mar 1997 20:06:05 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.5/8.7.3) id VAA16383; Sat, 29 Mar 1997 21:06:02 -0700 (MST) From: Ade Barkah Message-Id: <199703300406.VAA16383@hemi.com> Subject: Re: your mail To: nsj@freefall.freebsd.org (Nate Johnson) Date: Sat, 29 Mar 1997 21:06:01 -0700 (MST) Cc: www@freebsd.org In-Reply-To: <199703300209.SAA28148@freefall.freebsd.org> from Nate Johnson at "Mar 29, 97 06:09:13 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-www@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What's the scoop on adding a file to the makefile for www? notes.sgml, > who lives in data/releases/2.2.1R, needs an entry. What's the filename > of the Makefile, so that I can do this myself in the future? Hi Nate, I just happened commit the necessary changes, but for the future, when you add a new releases directory, you need to: 1) Add a Makefile in that new directory. The filename (easily enough) should be "Makefile". You can simply copy the Makefile from one of the other release subdirectories and modify it to suit your needs (modify the DOCS variable to contain all the .sgml pages in this new directory.) So, the 2.2.1R Makefile will look like: DOCS= notes.sgml .include "../../web.mk" Also do the 'cvs add Makefile ' as appropriate. 2) Modify www/data/releases/Makefile, so its SUBDIR variable contains the new directory. The line looks something like: SUBDIR= 1.1 1.1.5 2.0 2.0.5A 2.0.5R (...etc...) so we just need to add "2.2.1R" at the end. Anyhow, when you have a chance, do a 'cvs update' within your cvs working directory and browse through the Makefiles in releases/ and its subdirectory. For new releases, try to html-ize the announcement (announce.html) and the README file, as well as the release notes. Then, in addition to the above: 3) Update www/data/includes.sgml (the a.latest.not and a.latest.ann macros needs to point to the new files), and 4) Update releases/index.sgml so the "Current Releases" reflect this new release. Move the old release to the "Past Releases" section. I haven't done step 3) nor 4) above... the net-lag from my machine to freefall is unbearable right now. =-( Thanks! -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - -------------------------------------------------------------------