Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
X-MimeOLE:	Produced By Microsoft Exchange V6.0.4712.0
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	RE: /setup.html please read
Date:	Fri, 2 Nov 2001 12:23:12 -0500
Message-ID:	<6EB31774D39507408D04392F40A10B2BC1FDBD@FDYEXC202.mgroupnet.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic:	/setup.html please read - feedback desired
Thread-Index:	AcFjkICgwoeXvIEISlmKFHvU0gba3AALxwlQ
From:	"Roth, Kevin P." <KPRoth AT MarathonOil DOT com>
To:	<cygwin-apps AT cygwin DOT com>
X-OriginalArrivalTime:	02 Nov 2001 17:23:12.0436 (UTC) FILETIME=[0C9B4740:01C163C3]
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id fA2HNRA32281

1)
Under "Package File Naming", I see "The first release of a
package for a given vendor version may optionally skip the 
suffix". I take that to mean that
    cURL-7.9-1.tar.gz
and
    cURL-7.9.tar.gz
are both acceptable? Is that true?

2)
Under "Making Packages", I think the "standard" for binary
packages is to leave off the initial "/" on filenames 
inside the tarball. E.g.:
    usr/doc/cURL-7.9/README
instead of
    /usr/doc/cURL-7.9/README
I think the point is to allow someone to expand the
binary package into some other location (besides "/")
if desired for whatever reason.

For one thing, I don't see this tradition documented in 
this section. For another, your examples (e.g.
/usr/doc/foo-vendor) have the initial slash included.


3)
I realize this one is kind of nit-picky, but the 4th
bullet under "Making Packages" mentions a "file"
named /usr/doc/foo-vendor, when in fact this should
call it a "directory".


4)
The oft-referenced texinfo-4.0 example on the cygwin ml
includes the specific commands that can be used to
"unapply" the foo-vendor-suffix.patch file; could you
add those commands to this file?


5)
Again under "Making packages", you said that the patch
file should extract to /usr/src/foo-vendor-suffix.patch.
The texinfo example says it should go at
/usr/src/foo-vendor-suffix/CYGWIN-PATCHES/foo-vendor-suffix.patch.

Which place is "correct"?


6) 
Again, not to be nit-picky; however your example of 
"foo-vendor-suffix" is a bit misleading. Most packages
use "package-version-suffix", and don't (necessarily)
mention the "Vendor" in the package's name. I suggest
using the more generic but hopefully more accurate
"package-version-suffix" verbage throughout the doc.


7) [last one for today...]
Under "Submitting a package", could we get the text
updated to mention that Christopher typically
uploads things FOR us? (at least, those of us like
me with just one little package).


Thanks for getting this started! It looks great!

--Kevin



-----Original Message-----
From: Robert Collins [mailto:robert DOT collins AT itdomain DOT com DOT au]
Sent: Friday, November 02, 2001 6:25 AM

I've added in some guidelines on making packages and submitting them for
inclusion to http://www.cygwin.com/setup.html.

Please read, and if I've got anything wrong, let me know! I've had to
make some of it up from unwritten rules, so there is a good chance I've
gotten bits wrong.

- Raw text -