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, 22 Jun 2005 12:09:26 -0400 (EDT) From: Jason Pyeron To: cygwin AT cygwin DOT com Subject: Re: setup alternatives In-Reply-To: <42B98BA3.8BA2F700@dessent.net> Message-ID: References: <42B98BA3 DOT 8BA2F700 AT dessent DOT net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-IsSubscribed: yes On Wed, 22 Jun 2005, Brian Dessent wrote: > 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 static link and boot strap a core with the installer. Just like installing linux from cd. > 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. hmmm.... will have to look in to this. 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. gosh darnit, I just want to upgrade cygwin via ssh. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Partner & Sr. Manager 7 West 24th Street #100 - - +1 (410) 808-6646 (c) Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. -- 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/