Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: From: "Buchbinder, Barry (NIH/NIAID)" To: "'cygwin AT cygwin DOT com'" Subject: RE: Package READMEs online? (Was Re: How to install an update of the library GMP in cygwin?) Date: Mon, 30 Aug 2004 08:47:34 -0400 MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes At Saturday, August 28, 2004 8:44 PM, Igor Pechtchanski wrote: > On Sat, 28 Aug 2004, Reini Urban wrote: > >> Igor Pechtchanski schrieb: >>> On Sat, 28 Aug 2004, Gerrit P. Haase wrote: >>>> [snip] >>>> Until then, I have a version online at >>>> my site, this works and was the base of the actual port done by >>>> the maintainer: http://anfaenger.de/cygwin/cygwin-1.5/gmp/ >>>> >>>> To build from source with my patch, be sure to read the README: >>>> http://anfaenger.de/cygwin/cygwin-1.5/gmp/README >>> >>> Hey, this is a really good idea. Would it be much of a chore to >>> make the package READMEs available on the Cygwin package search >>> page, along with the contents? I'm mostly asking whether it'll >>> create a space problem of some sort, and whether the script that >>> builds the package list files for package-cat.cgi and >>> package-grep.cgi could be made to also extract the READMEs from the >>> packages and link to them online. FWIW, I couldn't find that >>> script in sourceware CVS -- I assume it's somewhere under infra/. >>> If someone points me to that script, I'm willing to give a shot to >>> writing the README extraction code. >> >> What about >> $ egrep "search-regex" /usr/share/doc/Cygwin/* >> >> Must everything be on the web? >> Maybe, because Google will not pickup the cygwin README's then. And >> people trust Google more than the content of their harddisc. > > It would also allow people to peruse the READMEs for Cygwin packages > that they haven't installed. > Igor While we're at it, a copy of setup.ini or the various setup.hints would also be useful. I often use an editor to look inside setup.ini for the "requires" or the "ldesc" and it would be easier if it was on the web site, maybe on http://sources.redhat.com/cygwin/packages/ - Barry -- 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/