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 Message-ID: <3CD1D978.2080701@ece.gatech.edu> Date: Thu, 02 May 2002 20:27:36 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Robert Collins CC: Stipe Tolj , cygwin-apps Subject: Re: rebasing new packages?! References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Robert Collins wrote: > >>-----Original Message----- >>From: Stipe Tolj [mailto:tolj AT wapme-systems DOT de] >>Sent: Friday, May 03, 2002 1:10 AM >>To: cygwin-apps >>Subject: rebasing new packages?! >> >> >>Hi there, >> >>could someone of the gurus arround tell a (half-)guru :)) >>what the standard way would be if packages have rebase problems? >> > > We either get Jasons in-setup-rebase patch into setup, or include a > command line rebase, and make your package require it, and your > postinstall script execute it. 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. --Chuck