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: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Mon, 2 Apr 2001 00:05:17 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: for interest: cygwin rpm on sourceforge Message-ID: <20010402000517.A535@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <200104020327 DOT XAA02347 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from ans@beethoven.cpe.ku.ac.th on Mon, Apr 02, 2001 at 10:55:43AM +0700 We have just had this discussion a week ago. You should probably go back and review the thread in the cygwin-apps archives. The subject was "setup wishes -- any volunteers". cgf On Mon, Apr 02, 2001 at 10:55:43AM +0700, Anon Sricharoenchai wrote: > >> 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.