Date: 31 Aug 2000 15:50:36 -0400
From: Lowell Gilbert <lowell@world.std.com>
To: freebsd-doc@freebsd.org
Subject: Re: HARDWARE.TXT vs. {i386,alpha}/RELNOTES.TXT
Message-ID: <444s41gqgj.fsf@lowellg.ne.mediaone.net>
In-Reply-To: "Bruce A. Mah"'s message of "Thu, 31 Aug 2000 12:01:35 -0700"
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> <200008311901.e7VJ1Zg03894@bmah-freebsd-0.cisco.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Bruce A. Mah" <bmah@FreeBSD.ORG> writes: > 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. Yes, it is. But the reverse isn't too bad: pull the text files into the docs from the main source tree. I see two main objections, both of which seem not only minor but eminently solveable: First, you wouldn't be able to use any markup on them. Second, you would be dependent on the presence of the text files, at least, from the src distribution. Eh? 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?444s41gqgj.fsf>