Date: Thu, 31 Aug 2000 12:01:35 -0700
From: "Bruce A. Mah" <bmah@FreeBSD.org>
To: Nik Clayton <nik@FreeBSD.org>
Cc: Jun Kuriyama <kuriyama@imgsrc.co.jp>, freebsd-doc@FreeBSD.org
Subject: Re: HARDWARE.TXT vs. {i386,alpha}/RELNOTES.TXT
Message-ID: <200008311901.e7VJ1Zg03894@bmah-freebsd-0.cisco.com>
In-Reply-To: <20000831105322.A66090@canyon.nothing-going-on.org>
References: <200008291834.e7TIYFm20218@bmah-freebsd-0.cisco.com> <20000829204112.A5240@luna.osd.bsdi.com> <20000830154508.A62946@canyon.nothing-going-on.org> <20000830173121.D17060@spirit.jaded.net> <7mbsy9dgdi.wl@waterblue.imgsrc.co.jp> <20000831105322.A66090@canyon.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] If memory serves me right, Nik Clayton wrote: > > Jade is too heavy to be included in build-release process. > > Not strictly true. If you build a release with the docs then Jade is > pulled down in to the chroot tree and installed. Hmmm. You're right. However, IMHO getting the .TXT files traditionally included in the release should not be dependent on building with docs. In other words, I build my releases with NODOC and NOPORTS, but I feel that I still ought to get, say, RELNOTES.TXT. We could, as a workaround, regenerate HARDWARE.TXT periodically and commit the output to the repository so it's available for a make release. But that's really grotesque. Bruce. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: b7MzhZvLhj2+8SbR5rwoztlYfarDP312 iQA/AwUBOa6rj9jKMXFboFLDEQJf8ACfYvBBe96mOR1vZsAkfBSnoZdur4AAoKhB vYPnvbqyFjPE03TKurGYRhTu =PL9+ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008311901.e7VJ1Zg03894>