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: 28 Dec 2001 13:12:38 -0500 Message-ID: <20011228181238.18279.qmail@lizard.curl.com> From: Jonathan Kamens To: cygwin-apps AT cygwin DOT com CC: cygwin-apps AT cygwin DOT com In-reply-to: <20011228181032.GA31028@redhat.com> (message from Christopher Faylor on Fri, 28 Dec 2001 13:10:32 -0500) Subject: Re: Robots binary package 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> <20011228181032 DOT GA31028 AT redhat DOT com> > Date: Fri, 28 Dec 2001 13:10:32 -0500 > From: Christopher Faylor > > I've never thought about this before but it makes no sense to me to have > rebuild instructions in the binary package. I don't have a problem with putting the rebuild instructions in the source package rather than the binary package. What I have a problem with is saying that there's no requirement to provide rebuild instructions *at all*. Perhaps we need to agree on a standard location where the rebuild instructions will go in the source package, update the Web page to document that location, and put instructions in that location from now on when building new or upgraded packages. jik