Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Fri, 28 Dec 2001 13:10:32 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: Robots binary package Message-ID: <20011228181032.GA31028@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <05bb01c18f64$5f3142d0$0200a8c0 AT lifelesswks> <20011228114125 DOT M27340 AT cygbert DOT vinschen DOT de> <065901c18f8d$05f2e650$0200a8c0 AT lifelesswks> <3C2C8729 DOT 91EDD8C6 AT yahoo DOT com> <20011228154829 DOT 16845 DOT qmail AT lizard DOT curl DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011228154829.16845.qmail@lizard.curl.com> User-Agent: Mutt/1.3.23.1i On Fri, Dec 28, 2001 at 10:48:29AM -0500, Jonathan Kamens wrote: >> Date: Fri, 28 Dec 2001 09:52:25 -0500 >> From: Earnie Boyd >> >> Your reference doesn't say that _ALL_ packages need a README. > >Quoting from : > > In your binary package, include a file > /usr/doc/Cygwin/foo-vendor-suffix.README containing (at a minimum) > the information needed for an end user to recreate the package. This > includes CFLAGS settings, configure parameters, etc. I've never thought about this before but it makes no sense to me to have rebuild instructions in the binary package. That's just cluttering up the disk space for 99% of the people who install the package. I could see the need for some kind of description about what the package is, but even there, I think that a man page would suffice. I agree with Corinna that there should be no absolute need for a README. Of course, I would say that because none of my packages have READMEs either... cgf