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 Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040427184642.03fcd240@pop.TheWorld.com> X-Sender: Date: Tue, 27 Apr 2004 18:48:48 -0400 To: cygwin AT cygwin DOT com From: Larry Hall Subject: Re: Anomalies in Source Distributions In-Reply-To: References: <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040422133723 DOT 038e2548 AT 127 DOT 0 DOT 0 DOT 1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 04:03 PM 4/27/2004, you wrote: >Op Thu, 22 Apr 2004 13:46:57 -0400 >schreef Larry Hall >in <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040422133723 DOT 038e2548 AT 127 DOT 0 DOT 0 DOT 1>: >: At 01:08 PM 4/22/2004, you wrote: > ^^^ >"Philip Brown" , not me. > >[...] >: > sharutils-4.2.1-3 - Similar to above for file: >: > /usr/share/doc/Cygwin/sharutils.README >: > which should be sharutils-4.2.1-3.README per your configuration system to >: > the best of my understanding. >: >: >: No. The prescribed approach from is: >: >: In your binary package, include a file /usr/share/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. >: >: This doesn't say any package version number is a requirement. There are >: benefits to leaving the number off (i.e. the same file applies to any >: version). > >Then, what is meant by ``-vendor-suffix'' in the above quotation? That would be the "4.2.1" for the sharutils example above. It's the upstream version numbers, not the Cygwin-specific release number. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/