This is the mail archive of the
mailing list for the Cygwin project.
Re: What comes with Cygwin?
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 14 May 2013 13:15:44 -0400
- Subject: Re: What comes with Cygwin?
- References: <CAHXt_SXEQCC8vS4jfU8fOTvEvAfCz=62FiiFQVqD05=6NouokA at mail dot gmail dot com> <51926146 dot 7030006 at etr-usa dot com> <20130514164456 dot GE3425 at ednor dot casa dot cgf dot cx> <51926D6C dot 8030900 at etr-usa dot com>
- Reply-to: cygwin at cygwin dot com
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple