public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Fergus Daly <ugly.leper@gmail.com>
Subject: Re: setup takes a long time
Date: Wed, 31 Jan 2018 14:02:00 -0000	[thread overview]
Message-ID: <f3941c58-e05a-7803-17c9-683ba0a32ddb@dronecode.org.uk> (raw)
In-Reply-To: <CAKqBF1igB-P_o__zbXwxKGtps_LaejHoQ_Qcp0OgUE2K5VjvUQ@mail.gmail.com>

On 31/01/2018 06:18, Fergus Daly wrote:
> The setup program does seem to take a long time, even when it just
> means "update" and even when there's nothing to update. Here's what
> happens in unattended mode:
> 
[...]

Try this with 'ts' from moreutils, e.g:

> $ ./setup-2.884.x86_64.exe --local-install '\\necker\download\cygwin-packages' --no-admin --upgrade-also --quiet-mode --mirror-mode --no-shortcuts | ts -i
> 00:00:00 Starting cygwin install, version 2.884
> 00:00:00 User has NO backup/restore rights
> 00:00:00 Current Directory: \\necker\download\cygwin-packages
> 00:00:00 Could not open Service control manager
> 00:00:00 root: C:\cygwin64 user
> 00:00:00 Selected local directory: \\necker\download\cygwin-packages
> 00:00:13 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_000_autorebase.dash"
> 00:01:40 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_texlive_prep.dash"
> 00:00:00 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_update-info-dir.dash"
> 00:00:03 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_adwaita-icon-theme.sh"
> 00:00:00 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_desktop-file-utils.sh"
> 00:00:00 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_fontconfig_cache_1.sh"
> 00:00:14 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_glib2.0.sh"
> 00:00:00 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_gnome-themes-standard.sh"
> 00:00:00 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_gnome-themes.sh"
> 00:00:00 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_hicolor-icon-theme.sh"
> 00:00:00 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_man-db.sh"
> 00:00:02 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_mate-icon-theme.sh"
> 00:00:00 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_mate-themes.sh"
> 00:00:00 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_shared-mime-info.sh"
> 00:00:00 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/zp_texlive_finish.dash"
> 00:00:02 Ending cygwin install
> I can kind of see the point of autorebase and update-info-dir, but why
> revisit texlive every time, and why all the zp stuff, every time? Why

These tasks are supposed to identify when they have no work to do, and 
do nothing quickly.  It seems that is not always the case.

> does setup explore McShield and McAfee? Incidentally note the switch
> -m. Without it, checking sha1sum's I guess provides some kind of
> protection, but it's incredibly time-consuming and seems quite
> unnecessarily to cover much more than the files downloaded, even the
> entire resource? In the presumably very rare event of a broken
> download, could the update not more simply just abort?

--local-install could indeed use some improvement.

Note that the scan is also used to filter the list of packages, so 
(without --mirror-mode) we don't offer for installation packages we 
don't have the archive for...

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-01-31 14:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  6:18 Fergus Daly
2018-01-31 14:02 ` Jon Turney [this message]
2018-01-31 14:58   ` Fergus Daly
2018-01-31 19:08     ` Achim Gratz
2018-01-31 15:34   ` Buchbinder, Barry (NIH/NIAID) [E]
2018-01-31 15:48     ` Brian Inglis
2018-01-31 19:06 ` Achim Gratz

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=f3941c58-e05a-7803-17c9-683ba0a32ddb@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=ugly.leper@gmail.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).