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: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: cURL packaging progress X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 Date: Tue, 16 Oct 2001 15:00:18 -0400 Message-ID: <6EB31774D39507408D04392F40A10B2BACC611@FDYEXC202.mgroupnet.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: cURL packaging progress Thread-Index: AcFWcaOLP7/cn0rXTluE+QhLKBE2gwAApeyg From: "Roth, Kevin P." To: "Gerrit P. Haase" Cc: X-OriginalArrivalTime: 16 Oct 2001 19:00:19.0024 (UTC) FILETIME=[CC804D00:01C15674] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id f9GJ2c904622 > -----Original Message----- > From: Gerrit P. Haase [mailto:gerrit AT familiehaase DOT de] > Sent: Tuesday, October 16, 2001 2:32 PM > To: Roth, Kevin P. > Subject: Re: cURL packaging progress > > > 4: Is there a commonly used "name" for cygwin binary tarballs? > > I'm trying to decide how to label the cygwin-specific > > "make" target. For example, cURL already has the ability > > to `make rpm` and `make pkgadd`. I'd like to add a > > `make cygwin-binary-tarball`, but don't know what to call it. > > It is the same as in unix curl-1.2.3-x.tar.gz > Main difference is the extension '-x' which is the release number. > Sources should also unpack into '1.2.3-x'. I had already realized this convention. My question had more to do with creating the build scripts. In Solaris, you have "pkgadd" modules, in Linux you have RPM's... In Cygwin, is there any standard name for a cygwin binary tarball? > > 5: I'd love to see the prefix of "/usr" coded into one of cURL's > > autotools-related files (configure.in?), so that, whenever > > configuring on (or for?) cygwin, I don't have to specify > > "--prefix=/usr" every time. Is there any commonly used method > > of doing this? It seems to me that this default should be > > hard-coded into auto-tools... > > No, don't do this, everyone who wants to build should be able to type > in --prefix=/usr if he likes to, default is always /usr/local. The binary cygwin installs should always install to /usr, but if someone downloads the source for a cygwin package and makes it themself, it will default to /usr/local. If they don't pay enough attention, they'll end up with two different copies installed (I did this with libtool by accident the first time). I assume then that this is normal behavior, and is considered to be "OK"? --Kevin