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
X-Authentication-Warning:	vivaldi.cpe.ku.ac.th: ans owned process doing -bs
Date:	Mon, 2 Apr 2001 10:55:43 +0700 (ICT)
From:	Anon Sricharoenchai <ans AT beethoven DOT cpe DOT ku DOT ac DOT th>
X-Sender:	<ans AT vivaldi DOT cpe DOT ku DOT ac DOT th>
cc:	<cygwin-apps AT cygwin DOT com>
Subject:	Re: for interest: cygwin rpm on sourceforge
In-Reply-To:	<200104020327.XAA02347@envy.delorie.com>
Message-ID:	<Pine.LNX.4.30.0104021047150.3200-100000@vivaldi.cpe.ku.ac.th>
MIME-Version:	1.0

> The key things that would need to be done first are:
>
> 1. Port the RPM library to MinGW (setup isn't a cygwin app).

Why don't make setup a cygwin app ?
Anyway, even though setup isn't a cygwin app, it can make call to rpm.exe
(which is a cygwin app) to install RPMs.

>
> 2. Teach setup to at least extract the files from the RPM (i.e. treat
>    the RPM as a fancy tar.gz file).  Use the library from #1 for this.
>
> That will at least let setup install RPMs, even if it doesn't keep an
> RPM database.  The next steps would be to do the RPM database and
> such, so that the cygwin-based RPM tools can interact nicely with what
> setup installs.
>

- Raw text -