From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Providing/Packaging a Postinstalled SUSV4 Doc only Package a la Debian
Date: Fri, 10 Mar 2017 20:24:00 -0000 [thread overview]
Message-ID: <87lgsc7ud3.fsf@Rainer.invalid> (raw)
In-Reply-To: <20170310201023.GA21500@calimero.vinschen.de> (Corinna Vinschen's message of "Fri, 10 Mar 2017 21:10:23 +0100")
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?
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.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2017-03-10 20:24 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 [this message]
2017-03-10 21:00 ` David Stacey
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=87lgsc7ud3.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).