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 Date: Wed, 26 Mar 2003 20:35:19 +0100 From: Marcel Telka To: cygwin AT cygwin DOT com Subject: Re: RPM-4.1 port to Cygwin available Message-ID: <20030326193519.GA3487@tortuga.etc.sk> References: <3E804EAB00011154 AT mss4n DOT bluewin DOT ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i On Wed, Mar 26, 2003 at 10:06:35AM -0800, Shankar Unni wrote: > 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). What about linking cygwin library statically into rpm (or apt-get) binary? -- +-------------------------------------------+ | Marcel Telka e-mail: marcel AT telka DOT sk | | homepage: http://telka.sk/ | | jabber: marcel AT jabber DOT sk | +-------------------------------------------+ -- 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/