From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Setup 2.774 texlive postinstall takes 10+ hours
Date: Tue, 04 Nov 2014 16:21:00 -0000 [thread overview]
Message-ID: <87bnonhr7z.fsf@Rainer.invalid> (raw)
In-Reply-To: <5457FBDD.4050408@cornell.edu> (Ken Brown's message of "Mon, 03 Nov 2014 17:04:13 -0500")
Ken Brown writes:
> That's now what I see here, unless I'm badly confused about what POSIX
> sort order is. I did an update a few days ago in which the
> postinstall scripts were run in the following order:
>
> update-info-dir.sh
> autorebase.bat
> wget.sh
Yes you are right. Sorry, I should have looked at it more thoroughly.
Anyway, I still think that we'd either should special-case autorebase
(like I do locally for this and other reasons) or introduce triggers and
trigger dependencies to setup. That would also make the texlive
postinstall a lot less time-consuming.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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
next prev parent reply other threads:[~2014-11-04 16:21 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 11:35 Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Martin.Fitzpatrick
2012-08-23 13:29 ` Earnie Boyd
2012-08-23 14:35 ` Adam Dinwoodie
2012-08-23 15:27 ` Ken Brown
2012-08-25 6:47 ` Ken Brown
2012-08-25 7:26 ` Achim Gratz
2013-01-28 16:42 ` toddcs
2013-01-29 3:41 ` Ken Brown
2013-02-05 15:48 ` jeremycraven
2013-02-05 16:37 ` marco atzeri
2013-02-05 16:43 ` Ken Brown
2013-02-06 9:52 ` jeremycraven
2013-02-06 14:11 ` Ken Brown
2014-07-20 14:01 ` leftwing
2014-07-20 17:44 ` Ken Brown
2014-10-20 22:39 ` Setup 2.774 texlive postinstall takes 10+ hours Don MacDougall
2014-10-21 2:09 ` Ken Brown
2014-10-21 2:26 ` Ken Brown
2014-10-21 4:06 ` Don MacDougall
2014-10-21 12:58 ` Ken Brown
2014-10-24 7:11 ` Don MacDougall
2014-10-24 11:35 ` Andrey Repin
2014-10-29 5:06 ` Don MacDougall
2014-10-29 12:20 ` Andrey Repin
2014-10-30 22:27 ` Don MacDougall
2014-11-02 18:02 ` Ken Brown
2014-11-03 10:25 ` Corinna Vinschen
2014-11-03 12:44 ` Ken Brown
2014-11-03 14:52 ` Corinna Vinschen
2014-11-03 16:17 ` Corinna Vinschen
2014-11-03 18:03 ` Achim Gratz
2014-11-03 22:04 ` Ken Brown
2014-11-04 16:21 ` Achim Gratz [this message]
2014-11-04 9:00 ` Corinna Vinschen
2014-11-11 4:23 ` Yaakov Selkowitz
2014-11-11 4:33 ` Yaakov Selkowitz
2014-11-11 11:53 ` Corinna Vinschen
2014-11-11 14:14 ` Ken Brown
2014-11-11 15:02 ` Ken Brown
2014-11-11 16:02 ` Corinna Vinschen
2014-11-11 17:08 ` Achim Gratz
2014-11-11 17:33 ` Corinna Vinschen
2014-11-11 18:39 ` Achim Gratz
2014-11-11 23:36 ` Ken Brown
2014-11-12 9:15 ` Corinna Vinschen
2014-11-12 17:53 ` Achim Gratz
2014-11-13 8:55 ` Corinna Vinschen
2014-11-13 19:41 ` Achim Gratz
2014-11-13 14:18 ` Setup 2.774 texlive postinstall takes 10+ hours) Corinna Vinschen
2014-11-13 15:45 ` Ken Brown
2014-11-13 16:18 ` Corinna Vinschen
2014-11-13 19:47 ` Achim Gratz
2014-10-21 3:23 ` Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Don MacDougall
2014-10-21 3:40 ` Don MacDougall
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=87bnonhr7z.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).