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: <3C20BBD0.3030502@ece.gatech.edu> Date: Wed, 19 Dec 2001 11:09:52 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin AT cygwin DOT com CC: Robert Collins Subject: Re: RPM 4 under cygwin References: <4 DOT 3 DOT 1 DOT 2 DOT 20011219103326 DOT 0166d180 AT pop DOT ma DOT ultranet DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Larry Hall (RFK Partners, Inc) wrote: >>2) Cygwin packages >>Could someone explain me what are the benefits of Cygwin packages over RPM. >>Do Cygwin packages test dependencies and validate signatures? 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. Signature validation is a good idea(*) -- Robert, can you add that to the wishlist? (*) I'm thinking more in terms the md5 file verification, not necessarily maintainer-signature PGP verification... --Chuck -- 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/