Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <3C41314E.50406@ece.gatech.edu>
Date: Sun, 13 Jan 2002 02:03:42 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: cygwin-apps AT cygwin DOT com
Subject: Re: ITP: libtool-devel, libtool-stable, libtool (wrappers)
References: <3C3C8A0E DOT 9000100 AT ece DOT gatech DOT edu> <20020109183309 DOT GB6261 AT redhat DOT com> <024601c1995d$304b3d10$0200a8c0 AT lifelesswks>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Robert Collins wrote:

> ----- Original Message -----
> From: "Christopher Faylor" <cgf AT redhat DOT com>
> 
> 
>>On Wed, Jan 09, 2002 at 01:21:02PM -0500, Charles Wilson wrote:
>>
>>>Preliminary versions are here:
>>>2) is "rc6" okay for a ${REL} number, or should it be a pure number?
>>>(p.s. 'rc' means "robert collins hack" not "release candidate")
>>>
>>upset will do the right thing with it.  I just checked.  It even seems
>>
> to
> 
>>properly support rc6 vs. rc7.
>>
>>I don't have any problems with it but it *is* a departure from the
>>guidelines in http://cygwin.com/setup.html, I believe.
>>
>>I'll let Robert make the executive decision on this one, I think.
>>
> 
> I'd prefer a pure number, but if you think folk will get seriously
> confused, then I guess rcx is ok.
> 
> In general, I'd prefer that 'flavours' get indicated in the package name
> (libtool_devel_rc-xxx-x-src.tar.bz2)


Okay, I've renamed the devel package:

libtool-devel-20010531-6

Again, it (and the others) are available at 
http://www.neuro.gatech.edu/users/cwilson/cygutils/testing/libtool/

The setup.hint files are appended below.

I still need some positive votes on this one....

--Chuck


libtool (wrappers):
================================
sdesc: "wrapper scripts for libtool-devel and libtool-stable"
ldesc: "GNU libtool is a generic library support script.
Libtool hides the complexity of using shared libraries behind
a consistent, portable interface.

libtool contains libtool-scripts-20010531, and is meant to be
installed alongside libtool-stable (which contains libtool-1.4.2)
and alongside libtool-devel (which contains a hacked
libtool-20010531).  It exec's the appropriate version based on
target package heuristics."
category: Devel
requires: ash libtool-devel libtool-stable

libtool-devel
================================
sdesc: "A shared library generation tool"
ldesc: "GNU libtool is a generic library support script.
Libtool hides the complexity of using shared libraries behind
a consistent, portable interface.

libtool-devel contains a modified version of libtool from
cvs (20010531) and supports `transparent' dll-building using
the new auto-import functionality of binutils.  libtool-devel
is meant to be installed alongside libtool-stable (which
contains libtool-1.4.2), and alongside the `libtool' package,
which contains wrapper scripts which call the appropriate
`real' libtool, stable or devel, based on target package
heuristics."
category: Devel
requires: cygwin ash automake autoconf libtool

libtool-stable
================================
sdesc: "A shared library generation tool"
ldesc: "GNU libtool is a generic library support script.
Libtool hides the complexity of using shared libraries behind
a consistent, portable interface.

libtool-stable contains libtool-1.4.2, and is meant to be installed
alongside libtool-devel (which contains Robert Collin's hacked-up
version of libtool-1.4, and supports `transparent' dll-building
using the new auto-import functionality of binutils), and alongside
the `libtool' package, which contains wrapper scripts which call
the appropriate `real' libtool, stable or devel, based on target
package heuristics."
category: Devel
requires: cygwin automake autoconf libtool ash