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
From: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Organization: convey Information Systems GmbH
To: "Roth, Kevin P." <KPRoth AT MarathonOil DOT com>, <cygwin-apps AT cygwin DOT com>
Date: Tue, 16 Oct 2001 21:22:58 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: RE: cURL packaging progress
Reply-to: cygwin-apps AT cygwin DOT com
Message-ID: <3BCCA532.13453.17EEA44@localhost>
In-reply-to: <6EB31774D39507408D04392F40A10B2BACC611@FDYEXC202.mgroupnet.com>
X-mailer: Pegasus Mail for Win32 (v3.12cDE)

> Roth, Kevin P. schrieb am 2001-10-16 15:00:

I don't know whether you are subscribed now, so I send you this mail 
directly, too, but please let us use 'only' the list, I'm subscribed
so I'm getting every mail twice.

>> > 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?
>

Not that I'm aware of at the moment.

>> > 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"?

Yes, if I build a package myself I will uninstall a cygwin package
before doing it.  But also I'm installing 'standard' packages always
in /usr so the original will be clobbered.

Gerrit

-- 
=^..^=