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>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <20020320132841.79750.qmail@web13704.mail.yahoo.com>
Date: Wed, 20 Mar 2002 05:28:41 -0800 (PST)
From: Stanislav Sinyagin <ssinyagin AT yahoo DOT com>
Subject: Packaging tools? (Was: RE: RFP: NASM)
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
Cc: CygWin-Apps <cygwin-apps AT cygwin DOT com>
In-Reply-To: <FC169E059D1A0442A04C40F86D9BA7600AFDD5@itdomain003.itdomain.net.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


--- Robert Collins <robert DOT collins AT itdomain DOT com DOT au> wrote:
> Please keep replies on-list.

sorry, sometimes mail comes with the list address in From:, 
but not this time...

> 
> And? Your points below don't give any rational that means NASM is good
> or bad to include. There are lots of things that only a few folk use in
> cygwin already - i.e. robots.
> 
> Other things also build smoothly - ie squid, grep, ls, sh-utils, bash,
> to name a few. So that's also not a good criterion.


well, grep, ls, bash are the must-be utilities, Cygwin wouldn't be what it is 
without them.

As for the packaging, the most annoing thing (only imho, I've built only 
one package, much less than you folks) was setting correctly all 
the path names in configure options, and then packing it all with a proper 
file name. 

Did someone think of developing a simple framework for making the packages, 
especially for that software which supports Cygwin and configure does everything
for you?

something like 
   cygmkpkg expat-1.95.2.tar.gz  
and that's it? 
Let the script do all unpacking, configuring, making, then packaging 
efforts? It would just prompt for the setup.ini description and category, 
or take them from previous version?

Then, after that, there will be no questions like "who's gonna maintain 
this package?" -- even the checkup for the sources version update can be
automated.

As for NASM, I've seen only one program which uses it (and can compile 
without it too) -- that's Lame. Are there more? Perhaps, some hardware 
related tools, like CD-R burning? Video processing?

Cheers, 
Stan

__________________________________________________
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/