Subject: Re: building docs on "make release"
To: None <hubert.feyrer@informatik.fh-regensburg.de>
From: Simon Burge <simonb@netbsd.org>
List: tech-install
Date: 03/01/2000 11:50:36
Hubert Feyrer wrote:

> On Tue, 29 Feb 2000, Eric Haszlakiewicz wrote:
> > Modified Files:
> > 	basesrc: Makefile
> > 
> > Log Message:
> > Add a buildmsg target for build to depend upon instead of using an ifmake block.  "make snapshot" now echos the start of build time.
> 
> This reminds me, I wondered why the INSTALL.* files were not created and
> put into $RELEASEDIR when I last tried my first "make release" - is there
> any good reason for it?
> 
> Is someone familiar enough with the twisty little maze of targets to add
> this?

The following would appear to DTRT, modulo deleting the building of the
notes that some ports (alpha, sparc, x68k) do by themselves.  I'll test
this out and commit it if it works ok.

Also, can we get rid of the extra parentheses on the

	(cd ..; ${MAKE} _DISTRIB= includes)

type lines?  Isn't each Makefile line run in it's own shell?

Simon.
--
Index: Makefile
===================================================================
RCS file: /cvsroot/basesrc/etc/Makefile,v
retrieving revision 1.136
diff -p -u -r1.136 Makefile
--- Makefile	2000/02/20 03:32:37	1.136
+++ Makefile	2000/03/01 00:46:30
@@ -241,7 +241,7 @@ release snapshot snap_pre snap_md_pre sn
 	@echo setenv RELEASEDIR before doing that!
 	@false
 .else
-release snapshot: distribution snap_pre snap_md_pre snap_kern snap_md_post
+release snapshot: distribution snap_pre snap_md_pre snap_kern snap_md_post notes
 	sh ../distrib/sets/maketars -s ../distrib/sets \
 		-d ${DESTDIR} -t ${RELEASEDIR}/binary/sets
 .if defined(CRYPTOPATH) && exists(${CRYPTOPATH})
@@ -307,6 +307,9 @@ snap_md_pre:
 
 snap_md_post:
 # nothing here -- look in the machine-dependent Makefile.inc
+
+notes:
+	cd ${.CURDIR}/../distrib/notes && ${MAKE} release
 
 .endif	# DESTDIR check