Message-ID: <4926261A.7070107@users.sourceforge.net>
Date: Thu, 20 Nov 2008 21:08:10 -0600
From: "Yaakov (Cygwin Ports)" <yselkowitz@users.sourceforge.net>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: cygwin-ports-general@lists.sourceforge.net, cygwin@cygwin.com
Subject: Re: new cygport feature: list-readme [patch]
References: <6910a60811140302h72c727t56adce8fbaa1d12@mail.gmail.com>
In-Reply-To: <6910a60811140302h72c727t56adce8fbaa1d12@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Reini Urban wrote:
> Attached is a patch against current stable 0.4.2, which adds list-readme,
> a list in README style format for all sub-packages.

Thanks for the patch.  I've been swamped with the Cygwin/X transition,
so I have yet to take a close look at this.

Sounds interesting, but I wonder if there is another way to do this
without actually tarballing each package.

> Maybe the new feature to support .list files should be better
> announced and described.

cygport as a whole needs to be documented.  I would prefer to use a
doxygen/gtk-doc type system to build documentation from the code and its
comments, but I'm not aware of any such system for bash.  Perhaps there
is, I just don't know.

> And maybe some helper is needed to detect changes in previous .list files.

Huh?


Yaakov
Cygwin Ports
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkmJhkACgkQpiWmPGlmQSOViACg0E9mCDxsMs71+NMXsPanfPeU
BnUAn2P5TxryppjaDnjvlSAkE60uwmml
=eoet
-----END PGP SIGNATURE-----

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