public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Buchbinder, Barry (NIH/NIAID) [E]" <barry.buchbinder@nih.gov>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: RE: setup takes a long time
Date: Wed, 31 Jan 2018 15:34:00 -0000	[thread overview]
Message-ID: <SN6PR0901MB252836923C954CBF94A6F3979BFB0@SN6PR0901MB2528.namprd09.prod.outlook.com> (raw)
In-Reply-To: <f3941c58-e05a-7803-17c9-683ba0a32ddb@dronecode.org.uk>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1067 bytes --]

Jon Turney sent the following at Wednesday, January 31, 2018 9:02 AM
>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:
>
> 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.

Recently brought up:
https://cygwin.com/ml/cygwin/2018-01/msg00274.html

It seems that this behavior is by design.
https://cygwin.com/ml/cygwin/2018-01/msg00275.html

FWIW, I still wouldn't mind having a command line option that skips
rebase and postinstall scripts when nothing has been updated.

Thanks,

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

  parent reply	other threads:[~2018-01-31 15:34 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
2018-01-31 14:58   ` Fergus Daly
2018-01-31 19:08     ` Achim Gratz
2018-01-31 15:34   ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
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=SN6PR0901MB252836923C954CBF94A6F3979BFB0@SN6PR0901MB2528.namprd09.prod.outlook.com \
    --to=barry.buchbinder@nih.gov \
    --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).