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 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: rebasing new packages?! X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Fri, 3 May 2002 09:47:51 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Stipe Tolj" , "cygwin-apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g42Nm1t23084 > -----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. Rob