Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<004c01c3293e$a70994c0$9f0c10ac@XYZZY>
From:	"Christopher B. Liebman" <liebman AT zod DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	rebase questions....
Date:	Mon, 2 Jun 2003 12:37:27 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1165

   What are the rules for *when* and on *what* to run rebase?  My project
builds a number of packages in it's own playpen (avoiding the system
versions so as not to get caught with system in various states of updates)
including perl, apache, mod_perl, tons of perl modules.  There are dll's
created for a number of these packages.  I know that I have to run rebase to
avoid issues at fork time.  I know about the rebaseall script....  should I
create my own local version of this that picks up *all* dlls in my local
playpen?  Do I need to include perl module .dlls? apache loadable modules?
Is there a ruleset or guideline document on rebase?  Thanks in advance.

    -- Chris



--
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/

- Raw text -