From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: Providing/Packaging a Postinstalled SUSV4 Doc only Package a la Debian
Date: Fri, 10 Mar 2017 21:00:00 -0000 [thread overview]
Message-ID: <cd8e64db-369c-3b72-299d-b013e2e266ff@tiscali.co.uk> (raw)
In-Reply-To: <87lgsc7ud3.fsf@Rainer.invalid>
On 10/03/17 20:24, Achim Gratz wrote:
> Corinna Vinschen writes:
>>> Otherwise, I am nervous about setting a precedent for a package that could
>>> give different contents each time it is installed (yes, Microsoft, I'm
>>> looking at you too). And there are plenty of corner cases where this
>>> wouldn't work: offline installs, web proxies, or if the account performing
>>> the Cygwin install (e.g. Administrator) was blocked from accessing the web
>>> (on security grounds).
>> This is another interesting point of course. Does wget or curl allow
>> to specify a (short) timeout before giving up and just not installing
>> anything, perhaps?
Yes. 'wget' has --timeout=<seconds>. You can also set --dns-timeout,
--connect-timeout and --read-timeout for fine-grain control [1].
However, the defaults are sensible and it gives up fairly quickly if
there's no network.
'curl' has --max-time and --connect-timeout [2].
> Regardless if that is possible (I think it is), I would not accept such
> a package into the standard distribution. For one, setup is not really
> equipped to handle such packages properly. Two, I really can't allow
> anything to download something from outside the internal network during
> the installation even where it might work.
I agree completely. I maintain what is effectively a private corporate
Cygwin Time Machine, so the company I work for can recreate
installations. Having this kind of repeatability is important to some
people. In one sense I can't get too excited - it's just a documentation
package afterall - I'm just nervous that it sets a precedent. What's
next? Similar packages for non-free fonts? How about a package that
downloads the 'lame' source, builds it and installs it, all from a
post-install script? These might sound a bit extreme, but you get my point.
Dave.
[1] - https://linux.die.net/man/1/wget
[2] - https://linux.die.net/man/1/curl
next prev parent reply other threads:[~2017-03-10 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 20:42 Brian Inglis
2017-03-10 15:43 ` David Stacey
2017-03-10 20:10 ` Corinna Vinschen
2017-03-10 20:24 ` Achim Gratz
2017-03-10 21:00 ` David Stacey [this message]
2017-03-17 19:41 ` Brian Inglis
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=cd8e64db-369c-3b72-299d-b013e2e266ff@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--cc=cygwin-apps@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).