Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <42B98BA3.8BA2F700@dessent.net> Date: Wed, 22 Jun 2005 09:02:43 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: setup alternatives References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Report: -5.9/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.0 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Jason Pyeron wrote: > yes, rpm and up2date. > > I was thinking this morning about writing a script to parse the setup.ini > and generate some no-src RPMs. > > It would be better if the RPMs were generated from src so dependencies > could be created 'properly'. I don't think it will be as simple as just converting the packages to rpm. The rpm command itself will depend on cygwin1.dll, and any subcommands that it executes (ls, awk, perl, whatever) will as well, in addition to any other DLLs that those commands need. This means you won't be able to install/remove any of those packages with rpm because it's impossible to replace in-use files under Windows and rpm does not know how to do it the windows-way. The last time I read of someone trying this it ended in rpm segfaulting and not working at all, but that could have been a while ago. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/