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: Sun, 1 Apr 2001 23:27:48 -0400
Message-Id: <200104020327.XAA02347@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: ans AT beethoven DOT cpe DOT ku DOT ac DOT th
CC: cygwin-apps AT cygwin DOT com
In-reply-to: <Pine.LNX.4.30.0104021032140.3200-100000@vivaldi.cpe.ku.ac.th>
	(message from Anon Sricharoenchai on Mon, 2 Apr 2001 10:34:34 +0700
	(ICT))
Subject: Re: for interest: cygwin rpm on sourceforge
References:  <Pine DOT LNX DOT 4 DOT 30 DOT 0104021032140 DOT 3200-100000 AT vivaldi DOT cpe DOT ku DOT ac DOT th>


> > There's no reason why setup can't use RPM to install files, if someone
> > wants to add RPM support to setup.  A lot of people have been
> > complaining that RPM isn't supported, yet nobody has offered to do the
> > work.
> 
> May be, I can do that work.  How can I contribute ?

The key things that would need to be done first are:

1. Port the RPM library to MinGW (setup isn't a cygwin app).

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.