Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Subject: setup doco
From: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
To: cygwin-developers AT cygwin DOT com
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.15 (Preview Release)
Date: 02 Nov 2001 13:44:44 +1100
Message-Id: <1004669085.5558.36.camel@lifelesswks>
Mime-Version: 1.0
X-OriginalArrivalTime: 02 Nov 2001 02:49:00.0019 (UTC) FILETIME=[EC879C30:01C16348]

I'm about to write up some doco on setup & related topics, covering
setup.exe
progamming setup.exe
setup.hint
creating packages
categories

Now, some of this - categories, setup.hint and creating packages isn't
strictly setup.exe dependent.

I'd like that stuff to be available as html from the website, to point
contributors to. (Rather than repeating it in the cygwin-apps list n
times).

I have a very useful XML/XSL docbook build environment that I really
like using, but it requires automake (1.4 or 1.5) - is there any issue
with me adding the documentation in cinstall/doco as a sub package? (I
use this on cygwin and on linux do generate doco).

If there is, I'll extract the relevant tests and handcraft it into the
current setup.exe configure.in and Makefile.in's.

Rob