Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <00c801c18932$d757cc30$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <jm DOT poure AT freesurf DOT fr>, <cygwin AT cygwin DOT com>
References: <4 DOT 3 DOT 1 DOT 2 DOT 20011219103326 DOT 0166d180 AT pop DOT ma DOT ultranet DOT com> <3C20BBD0 DOT 3030502 AT ece DOT gatech DOT edu> <200112200844 DOT fBK8iQx13965 AT www1 DOT translationforge>
Subject: Re: RPM 4 under cygwin
Date: Thu, 20 Dec 2001 19:46:38 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 20 Dec 2001 08:47:10.0807 (UTC) FILETIME=[E9DD9E70:01C18932]

Then why not help us get deb/rpm support into setup.exe rather than just
complaining that we don't understand.

This HAS been covered. Many times. It's in the archives. RPM as static
port is *not good enough*. Neither is dpkg. As a userland tool for
building packages, yes, but thats a different story.

Rob

...
There are 100 times more Linux developpers than $Windows developpers.
Why
to reinvent the wheel with another installation format? Do you really
think
you can create a universal format including DEB and RPM? Then you need
to
produce more work than the creators of these formats. This is such a
difficult project...




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/