DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=w3383JOgzhW+4Im5hfKNiwThCcwMxXHaaozlsMaTWDD3G+Caz1jf6
	+M+9wIGgGddsANzN/TGXY6zDE48eBS64ad1Q4fmoxncbpRXFUsy5YJe51YWO2JKG
	6TyvTh9UlUNyn5sneTZPNxcQj8ShqO9pLwUb/9K7lQBQMG8Ll7mGBY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 14 May 2013 13:15:44 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: What comes with Cygwin?
Message-ID: <20130514171544.GA4016@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAHXt_SXEQCC8vS4jfU8fOTvEvAfCz=62FiiFQVqD05=6NouokA@mail.gmail.com> <51926146.7030006@etr-usa.com> <20130514164456.GE3425@ednor.casa.cgf.cx> <51926D6C.8030900@etr-usa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51926D6C.8030900@etr-usa.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Tue, May 14, 2013 at 10:59:24AM -0600, Warren Young wrote:
>On 5/14/2013 10:44, Christopher Faylor wrote:
>>I don't think the documentation should be considered the definitive
>>source for this since it is likely to change over time and the
>>documentation is likely to be out of date.
>
>It wouldn't be too hard to take this a few steps further and completely
>automate the process of building that list.  Then it could be a make
>target in the docs, generating an .xml fragment file that's XIncluded
>into the docs somewhere.
>
>You'd probably have to check the fragment into CVS and periodically
>regenerate it on a Cygwin system, since you probably can't build it on
>a Linux box, since it depends on being able to run cygcheck.
>
>The generator can date the output, too: "As of May 14, 2013..."

Or, use setup.exe to check the "Base" category and find out immediately
what's going to be installed.  I don't see why it is important to have
potentially out-of-date information listed in the documentation when you
are going to be running setup.exe eventually anyway and you can get
the definitive list there.

If web access is really a must-have, another possibility would be to
offer a category view in the cygwin package lister.  Then the
documentation could link to that.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple