Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <200112200844.fBK8iQx13965@www1.translationforge> Content-Type: text/plain; charset="iso-8859-1" From: Jean-Michel POURE Reply-To: jm DOT poure AT freesurf DOT fr Organization: Translationforge To: cygwin AT cygwin DOT com Subject: Re: RPM 4 under cygwin Date: Thu, 20 Dec 2001 09:44:25 +0100 X-Mailer: KMail [version 1.3.1] 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> In-Reply-To: <3C20BBD0.3030502@ece.gatech.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id fBK8inJ05605 > Since Larry didn't touch this, I'll respond.  Cygwin packages can be unpacked/interpreted/understood by a NON cygwin program (setup.exe is a native windows app).  ALL ports of RPM that I have seen require cygwin -- which means they cannot easily be used to install cygwin itself on a virgin system.  This is a serious drawback. This clearly is a demonstration that cygwin would benefit from a static compilation option. I know this is not an issue for you all, but ... Coming back to RPM, this would be so nice to issue this command: rpm --rebuild --target=cygwin package_name.rpms to compile any existing apckage for Cygwin. 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... Best regards, Jean-Michel POURE -- 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/