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
Date: Tue, 21 Nov 2000 13:48:47 -0500 (EST)
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
X-Sender: cwilson AT frontal DOT ibb DOT gatech DOT edu
To: DJ Delorie <dj AT delorie DOT com>
cc: cygwin-apps AT cygwin DOT com
Subject: Re: New versions of bzip2 and patch?
In-Reply-To: <200011211505.KAA17222@envy.delorie.com>
Message-ID: <Pine.GSO.4.20.0011211348190.1273-100000@frontal.ibb.gatech.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

DJ Delorie wrote:

>> shouldn't the other tarball, bzip2.tar.gz, be listed as the current
>> release?  Or do you have to specify [current] as well as [test] in the
>> setup.hint file?
> 
> 
> You have to specify everything if you specify anything.  It won't
> default anything once a setup.hint is found.

Okay, so how do I specify that "bzip2.tar.gz" (no versioning at all) is
the current release?

current 0.0.0 ?

--Chuck