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: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <001f01c1e905$efa327c0$0200a8c0@lifelesswks> From: "Robert Collins" To: "Charles Wilson" Cc: References: <3CC26486 DOT 3000705 AT ece DOT gatech DOT edu> Subject: Re: strange source packaging? Date: Sun, 21 Apr 2002 17:27:03 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 21 Apr 2002 07:27:02.0482 (UTC) FILETIME=[EE46F320:01C1E905] All the content changes look great however. If you can clean up the space to tab conversion, I'm happy for this to go in. However as it's a change to the standard... Any objections from any contributor? Rob (see below for the tab occurences) === ----- Original Message ----- From: "Charles Wilson" To: "Robert Collins" Cc: Sent: Sunday, April 21, 2002 5:04 PM Subject: Re: strange source packaging? > > Can we get a diff for the HTML page? > > Okay.... Thanks... > -standard Cygwin setup program. This documents the syntax of the > +standard Cygwin setup program. This documents the syntax of the This change (not eye-visible) is wrong - Tabs have no meaning in HTML. Mind you double spaces don't mean all that much either :}. However Tabs are definately wrong. > -on certain conventions being followed. If they are not followed, bad > +on certain conventions being followed. If they are not followed, bad Ditto. > -

Source tar files are named "package-version-src.tar.bz2". Source tar files > -should contain the source files needed to rebuild the package. While > +

Source tar files are named "package-version-release-src.tar.bz2". Source tar files > +should contain the source files needed to rebuild the package. While Ditto for the second line. (What editor are you using?) > -the introducing field. This usage is allowed but deprecated. Please > +the introducing field. This usage is allowed but deprecated. Please And again.. > -different from the name of the directory in which the package resides. This > +different from the name of the directory in which the package resides. This And... here. > -prev. Otherwise, the only version that setup.exe will > +prev. Otherwise, the only version that setup.exe will Guess what.. :}. > -above. Uses arrow keys for positioning over moles. Space > +above. Uses arrow keys for positioning over moles. Space I've included all these for completeness, not to be a pain. They need to get fixed before committing. > -word. We don't anticipate that this will change anytime soon. However, > +word. We don't anticipate that this will change anytime soon. However, Another. > -This line follows the setup-timestamp in all setupl.ini files. It > +This line follows the setup-timestamp in all setupl.ini files. It Guess what. > -This is the "long description" of the package. This text, if > +This is the "long description" of the package. This text, if And... > -One package can belong to multiple categories. Multiple categories are > +One package can belong to multiple categories. Multiple categories are Some more. > -The requires line indicates the packages that this package belongs to. A > -package can rely on multiple packages. Multiple packages are separated > +The requires line indicates the packages that this package belongs to. A > +package can rely on multiple packages. Multiple packages are separated Hmm.. :} > -run is not guaranteed. Therefore, if your package depends on others > +run is not guaranteed. Therefore, if your package depends on others Finally Rob