public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Peter A. Castro" <doctor@fruitbat.org>
To: cygwin@cygwin.com
Subject: Re: New setup pre-release - feedback needed
Date: Wed, 17 Jul 2002 03:11:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0207162353170.8342-100000@gremlin.fruitbat.org> (raw)
In-Reply-To: <074301c22a77$251a7180$2300a8c0@LAPTOP>

On Sun, 14 Jul 2002, Robert Collins wrote:

> We're coming up on a new release of setup.exe, with a number of user
> interface enhancements to make it more obvious what setup is doing when it
> 'pauses'.

While I do like the status of knowing just what setup is scanning as part
of the package loading process, it now takes much, much longer to load
from an "Install from Local Directory" scenario :-) (up from 5 seconds to
about 1 minute, 45 seconds).  It's a kind of a rare scenario (I'm
probably one of the few who keeps a full downloaded image of all of
cygwin (kinda like a mirror site)), and it's not like I run setup more
than once every few days, so it's an adequate trade-off for more status
on the package load. 

> It *should* be bug free, although there may be a minor bug with
> autodetection of upgrades (we have one report, but no debugging info).

I did some test installs and re/de-installs and it appears to work well.
The only thing I did notice was that during the actual package
installation part, the Progress bar is showing "full" when it's installed
only about 3/4ths of the files from the package.  I noticed this more
with source packages than binaries, but did see it a few times with some
binary-only package installs.  It's really just a cosmetic thing and
didn't seem to effect the actual installation.  I view it as a reversal
of the old '98% finished' phenomenon :-)

> The pre-release snapshot can be found at
> http://www.cygwin.com/setup-snapshots/setup-2.259.2.4.exe.
> 
> As usual, the quality of this release will depend on feedback from you, the
> users. Please give the new version a go, and if you have *any* trouble, send
> me the setup.log and setup.log.full from your run of setup.exe.

I haven't tried a full reload of cygwin (might try that later), but doing
a few minor updates and a few re/de-installs did not turn up any
problems.  Looking good!

> Cheers,
> Rob

-- 
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
	"Cats are just autistic Dogs" -- Dr. Tony Attwood


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2002-07-17  7:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-13 12:21 Robert Collins
2002-07-15 22:13 ` Joerg R. Schaible
2002-07-17  3:11 ` Peter A. Castro [this message]
2002-07-17  3:24   ` Robert Collins
2002-07-18  2:42     ` Peter A. Castro
2002-07-17 11:59   ` Max Bowsher
2002-07-16  8:22 Demmer, Thomas
2002-07-16  8:41 ` Robert Collins
2002-07-16 13:18 Harig, Mark A.
2002-07-16 14:36 ` Max Bowsher
2002-07-17  3:26   ` Robert Collins
2002-07-17 11:43     ` Max Bowsher
2002-07-16 18:18 ` Robert Collins
2002-07-17  6:56 John Vincent
2002-07-17  9:26 Harig, Mark A.
2002-07-17  9:56 ` Robert Collins
2002-07-17 10:12 Harig, Mark A.
2002-07-17 11:25 Harig, Mark A.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.21.0207162353170.8342-100000@gremlin.fruitbat.org \
    --to=doctor@fruitbat.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).