Satish,
On Thu, Oct 27, 2005 at 03:04:52PM -0500, Satish Balay wrote:
> On Thu, 27 Oct 2005, Jason Tishler wrote:
> > On Thu, Oct 27, 2005 at 02:15:01PM -0500, Satish Balay wrote:
> > > I've tried using python after doing a complete 'reinstall' and so
> > > far It works fine. I'll keep track of an
On Thu, 27 Oct 2005, Jason Tishler wrote:
> Satish,
>
> On Thu, Oct 27, 2005 at 02:15:01PM -0500, Satish Balay wrote:
> > I've tried using python after doing a complete 'reinstall' and so far
> > It works fine. I'll keep track of any future breakages.
> >
> > It will be great if rebase is not re
Satish,
On Thu, Oct 27, 2005 at 02:15:01PM -0500, Satish Balay wrote:
> I've tried using python after doing a complete 'reinstall' and so far
> It works fine. I'll keep track of any future breakages.
>
> It will be great if rebase is not required at all...
The following is a good test:
$ py
On Wed, 26 Oct 2005, Brian Dessent wrote:
> Satish Balay wrote:
>
> > According to Jason's post, --enable-auto-image-base is been in use for
> > a while. [Since python doesn't always work without rebaseall] - is
> > there some other issue with this approach? [mabye some dependent
> > package sho
On Wed, 26 Oct 2005, Satish Balay wrote:
> On Tue, 25 Oct 2005, Brian Dessent wrote:
>
> > As far as I know almost all of the issues of corrupted DLLs have been
> > fixed, but there still remains at least one known problem: emacs will
> > hang and refuse to start after running rebaseall, unless y
Satish Balay wrote:
> According to Jason's post, --enable-auto-image-base is been in use for
> a while. [Since python doesn't always work without rebaseall] - is
> there some other issue with this approach? [mabye some dependent
> package should be built with --enable-auto-image-base - but it isn
On Tue, 25 Oct 2005, Brian Dessent wrote:
> Satish Balay wrote:
>
> > - open a dialog box with a message:
> > "some packages that require 'rebaseall' are updated. This operation
> > cannot be done at this time due to active cygwin processes. Please
> > reboot, shutdown cygwin services, and ru
On Tue, 25 Oct 2005, Brian Dessent wrote:
> As far as I know almost all of the issues of corrupted DLLs have been
> fixed, but there still remains at least one known problem: emacs will
> hang and refuse to start after running rebaseall, unless you revert
> cygncurses-7.dll to its non-rebased ve
Satish Balay wrote:
> - open a dialog box with a message:
> "some packages that require 'rebaseall' are updated. This operation
> cannot be done at this time due to active cygwin processes. Please
> reboot, shutdown cygwin services, and run 'rebaseall' from 'ash'."
The thing is, you can't just
Satish Balay wrote:
> Doesn't setup have similar problem with updating 'packages' for
> running apps? I think it prompts for a reboot to complete. So I'm
> guessing the same approach can be used when it needs a rebase.
Yes, of course setup already has that logic. That's what I was
referring to a
Satish Balay wrote:
> So the curent assesment is :
>
> - python - and similar tools can break - is so use rebase to fix it.
> - rebase is broken - is lets not use it all the time.
As far as I know almost all of the issues of corrupted DLLs have been
fixed, but there still remains at least one
On Tue, 25 Oct 2005, Christopher Faylor wrote:
> >And Jason's post was in Feb-2002 - and things have been in this bad
> >state since a long time.
>
> And, yet, somehow, we survive.
But at a cost of regular user frustation - which I was hoing could be
avoided.
>From the replies so far - it appea
On Tue, Oct 25, 2005 at 11:41:05AM -0500, Satish Balay wrote:
>On Tue, 25 Oct 2005, Igor Pechtchanski wrote:
>
>> Plus, as Jason mentions, rebasing corrupts some DLLs. So, until a robust
>> solution for that is found, automatically rebasing in setup.exe isn't such
>> a hot idea.
>
>So the curent a
On Tue, 25 Oct 2005, Dave Korn wrote:
> Satish Balay wrote:
>
> > Doesn't setup have similar problem with updating 'packages' for
> > running apps? I think it prompts for a reboot to complete. So I'm
> > guessing the same approach can be used when it needs a rebase.
>
> It's not as straightfor
On Tue, 25 Oct 2005, Igor Pechtchanski wrote:
> Plus, as Jason mentions, rebasing corrupts some DLLs. So, until a robust
> solution for that is found, automatically rebasing in setup.exe isn't such
> a hot idea.
So the curent assesment is :
- python - and similar tools can break - is so use r
Satish Balay wrote:
> Doesn't setup have similar problem with updating 'packages' for
> running apps? I think it prompts for a reboot to complete. So I'm
> guessing the same approach can be used when it needs a rebase.
It's not as straightforward as all that. The facility to update a file on
r
On Mon, 24 Oct 2005, Brian Dessent wrote:
> Automatically running rebaseall from setup.exe has issues too. For one
> thing, it would run into problems if the user had programs or services
> running. The rebaseall script bails if it cannot write to a DLL, so
> unless the user was very careful to
On Mon, 24 Oct 2005, Brian Dessent wrote:
> Satish Balay wrote:
>
> > [maybe the fix is: for any package that is likely to break - add a
> > flag - which triggers setup to run rebaseall - after
> > install/upgrade. So no overhead for pacakges that don't break - but
> > always overhead for packages
On Mon, Oct 24, 2005 at 09:57:21PM -0700, Brian Dessent wrote:
> Satish Balay wrote:
> > Ok so the problem is likely to go away for python users.
>
> I don't know if Jason has started compiling Python with
> --enable-auto-image-base or not.
I have been using --enable-auto-image-base since the ver
Satish Balay wrote:
> Ok so the problem is likely to go away for python users.
I don't know if Jason has started compiling Python with
--enable-auto-image-base or not. It will also depend on the maintainers
of any libraries that are dynamically loaded by a python module using
the flag as well.
On Mon, 24 Oct 2005, Brian Dessent wrote:
> Additionally, maintainers of these packages have (I believe) recently
> started compiling them with --enable-auto-image-base which should
> eliminate (or reduce) the need to rebase.
Ok so the problem is likely to go away for python users.
>
> > [for o
Satish Balay wrote:
> Q: Does cygwin setup run rebaseall either during initial install or
> during subsequent updates? [guessing no]
No, setup has no clue about rebaseall.
> Q: Is it safe to say: 'if cygwin is installed from scratch - rebaseall
> is not required'
That's not quite correct. Whet
I don't see any FAQ regarding rebaseall - hence this post.
It appears that rebaseall is required ocassionally to get cygwin [esp
python] working. [having been bitten by this a few times,] Each time I
do any cygwin updates - I make sure I run 'rebaseall' before doing
anything else.
Q: Does cygwin
23 matches
Mail list logo
