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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Shankar Unni Subject: Re: RPM-4.1 port to Cygwin available Date: Wed, 26 Mar 2003 10:06:35 -0800 Lines: 25 Message-ID: References: <3E804EAB00011154 AT mss4n DOT bluewin DOT ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en In-Reply-To: <3E804EAB00011154@mss4n.bluewin.ch> Yann Crausaz wrote: > The version of setup.exe I propose must be a bit old, isn't it ? If there's > a real interest, I'm OK to care about the latest version, but will poeple > really use RPM under Cygwin ? Good point. The real benefit to porting RPM or apt-get or whatever to Windows is as a possible replacement for the current installation system (if anyone considers RPM, and its associated GUIs, an improvement, that is). For that, however, these programs need to be *native Windows binaries* (i.e. no cygwin layer underneath), or you'd have a chicken-and-egg problem doing a first-time installation (or any time you updated cygwin itself). So for the moment, these ports are mainly a curiosity. Perhaps one future idea may be for the cygwin installations can be split up into the Base group installed by the current setup, and RPM/apt-get or whatever to manage the rest? -- Shankar. -- 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/