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: <3C989DF4.69B4774F@hack.kampbjorn.com>
Date: Wed, 20 Mar 2002 15:34:28 +0100
From: Hack =?iso-8859-1?Q?Kampbj=F8rn?= <cygwin-apps AT hack DOT kampbjorn DOT com>
Reply-To: cygwin-apps AT cygwin DOT com
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,da,es,ca
MIME-Version: 1.0
To: Stanislav Sinyagin <ssinyagin AT yahoo DOT com>
CC: CygWin-Apps <cygwin-apps AT cygwin DOT com>
Subject: Re: Packaging tools? (Was: RE: RFP: NASM)
References: <20020320132841 DOT 79750 DOT qmail AT web13704 DOT mail DOT yahoo DOT com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Stanislav Sinyagin wrote:
> 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?

Chuck did write a script that automatizes most of these steps. You can
call it a framework since all his new packages uses this script (and so
does mine). Take a look at one of them.

There was a long discussion about packaging and package management. But
we don't want to reinvent the wheel and implement a rpm-like or
dpkg-like infrastructure. IIRC a decision was postponed till setup.exe
could be used to bootstrap one of the already existent packaging
systems.

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

-- 
Med venlig hilsen / Kind regards

Hack Kampbjørn