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 Date: Tue, 25 Oct 2005 14:31:40 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin-setup & rebaseall Message-ID: <20051025183140.GA19220@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <435D743F.EDB6FBB9@dessent.net> <435DBB31.5C164C83@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Tue, Oct 25, 2005 at 11:41:05AM -0500, Satish Balay wrote: >On Tue, 25 Oct 2005, Igor Pechtchanski wrote: > >> Plus, as Jason mentions, rebasing corrupts some DLLs. So, until a robust >> solution for that is found, automatically rebasing in setup.exe isn't such >> a hot idea. > >So the curent assesment is : > > - python - and similar tools can break - is so use rebase to fix it. > - rebase is broken - is lets not use it all the time. > >[so it appears cygwin can always be in broken state - this is not good] > >And Jason's post was in Feb-2002 - and things have been in this bad >state since a long time. And, yet, somehow, we survive. cgf -- 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/