Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Date: Fri, 15 Jul 2005 07:27:27 -0400
From: Jason Tishler <jason AT tishler DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: rebaseall (was Re: Perl Win32::Shortcut screws up fork)
Message-ID: <20050715112727.GA2864@tishler.net>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <42CDD3B8 DOT 69B6AB98 AT dessent DOT net> <20050708011859 DOT GB24841 AT trixie DOT casa DOT cgf DOT cx> <42CDD9CB DOT 8390A097 AT dessent DOT net> <20050708020511 DOT GA1718 AT trixie DOT casa DOT cgf DOT cx> <42CDE3D4 DOT 6030507 AT byu DOT net> <20050708035038 DOT GB2123 AT trixie DOT casa DOT cgf DOT cx> <20050711124307 DOT GB3856 AT tishler DOT net> <20050712020833 DOT GB17886 AT trixie DOT casa DOT cgf DOT cx> <20050714115552 DOT GB3304 AT tishler DOT net> <20050714200108 DOT GD24167 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050714200108.GD24167@trixie.casa.cgf.cx>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes

On Thu, Jul 14, 2005 at 04:01:08PM -0400, Christopher Faylor wrote:
> On Thu, Jul 14, 2005 at 07:55:52AM -0400, Jason Tishler wrote:
> >On Mon, Jul 11, 2005 at 11:50:08PM -0400, Christopher Faylor wrote:
> >> OTOH, writing a mingw C program to do what rebaseall does wouldn't
> >> be *that* hard.
> >
> >Agreed.
> >
> >I would like to go with this approach except rewrite rebaseall as a
> >Cygwin C program with the Cygwin DLL as its only dynamic dependency.
> >However, given my limited free time, it may be a while before I can
> >develop a C-based rebaseall.  So, what is the best short-term
> >solution?  Should I just release a new package with the following
> >patch:
> >
> >    http://cygwin.com/ml/cygwin/2005-07/msg00319.html
> >
> >applied?
> 
> How about if for now you just make it an ash script (meaning that it
> relies on ash) and use your technique of checking for other cygwin
> processes running?  If "we" are going to make this a program anyway,
> eventually, then I don't mind just using your technique which is
> really more foolproof than mine.  No matter how this is implemented,
> checking that no cygwin processes are running before running rebaseall
> has to be a good idea.

I'm glad we agreed.  I will implement the above.

> If we do make this a program, maybe it should just be an extension to
> rebase itself: "rebase --all" ?

Exactly!  Right after my previous post, I started to investigate
enhancing rebase to support rebaseall functionality.  I quickly realized
that this change would not require too much effort.

I will also enhance rebase so if it is invoked as rebaseall, then the
"--all" option is implied.

So, it sounds like we have short and long term plans.  Now, I just have
to work 'em.

Thanks,
Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

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