Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Fri, 03 May 2002 09:34:16 -0400 From: Jason Tishler Subject: Re: rebasing new packages?! In-reply-to: To: cygwin-apps AT cygwin DOT com Mail-followup-to: cygwin-apps AT cygwin DOT com Message-id: <20020503133416.GC3216@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.3.24i References: On Fri, May 03, 2002 at 10:31:48AM +1000, Robert Collins wrote: > > -----Original Message----- > > From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu] > > Sent: Friday, May 03, 2002 10:28 AM > > > I thought that the last time this subject came up, the consensus was > > that Jason's code should go into the cinstall area (now, of > > course, that > > means the setup repository). The standalone rebase.exe > > should be built > > within that project, along with setup.exe which would > > leverage the same > > code. > > > > That way, there's no possibility that the two programs would get > > out-of-sync with respect to the /etc/rebase.conf (?) information and > > file format. > > Yes, and at that point we had two issues: > 1) We couldn't use libstdc++, let alone the STL. The STL still isn't > available - beyond whats in libg++-3. Having STL would really speed things up. When I saw you adding libstdc++, I thought implied STL but I was mistaken. Can we enable STL for setup.exe? > 2) I think that Jason's design needed some tweaking. Yes, mainly in the area of how I persisted the free and used lists. Additionally, another major issue to resolve is how to deal with DLLs that get corrupted by rebasing. Jason