This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: rebasing new packages?!
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- To: Robert Collins <robert dot collins at itdomain dot com dot au>
- Cc: Stipe Tolj <tolj at wapme-systems dot de>,cygwin-apps <cygwin-apps at cygwin dot com>
- Date: Thu, 02 May 2002 20:27:36 -0400
- Subject: Re: rebasing new packages?!
- References: <FC169E059D1A0442A04C40F86D9BA7600C5F98@itdomain003.itdomain.net.au>
Robert Collins wrote:
>
>>-----Original Message-----
>>From: Stipe Tolj [mailto:tolj@wapme-systems.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