public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: units issues
Date: Wed, 24 May 2017 18:06:00 -0000	[thread overview]
Message-ID: <8760gq5dv1.fsf@Rainer.invalid> (raw)
In-Reply-To: <6CF2FC1279D0844C9357664DC5A08BA23D259840@msgb10.nih.gov> (Barry	Buchbinder's message of "Wed, 24 May 2017 16:26:48 +0000")

Buchbinder, Barry (NIH/NIAID) [E] writes:
> I would prefer that by default updates happen automatically and those
> who do not want automatic updates do something to stop them from
> happening.

That there should be updates was never debated, only the machanism of
doing so is discussed here.

> For instance, someone who does not want updates makes the
> definitions file read-only and have the script check for write
> permission and exit or skip updating if the file cannot be written.  A
> zero length read-only file works if one is worried about someone using
> stale conversion factors.  An environmental variable whose existence
> marks no-update might be another possibility.

No again.  In general, it is a no-no to alter or remove files that came
with the package (besides, the user might not even be able to, depending
on how Cygwin gets installed).  Cygwin isn't very fussy about such
errors at the moment, but that shouldn't be an excuse to become sloppy.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

  parent reply	other threads:[~2017-05-24 18:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 22:42 [ITA] units Brian Inglis
2017-04-26  2:25 ` Yaakov Selkowitz
2017-04-26  2:59   ` Brian Inglis
2017-04-26 13:17     ` Jon Turney
2017-04-26 15:51     ` Brian Inglis
2017-04-26 18:30       ` Yaakov Selkowitz
2017-04-26 23:16         ` Brian Inglis
2017-04-26 23:20           ` Brian Inglis
2017-04-27 11:51             ` Jon Turney
2017-04-27 18:37               ` Brian Inglis
2017-04-27 23:31                 ` Brian Inglis
2017-05-22 20:58                 ` units issues Brian Inglis
2017-05-23 17:28                   ` Achim Gratz
2017-05-23 21:49                     ` Brian Inglis
2017-05-23 23:55                       ` Doug Henderson
2017-05-24  2:37                         ` Brian Inglis
2017-05-24 16:26                           ` Buchbinder, Barry (NIH/NIAID) [E]
2017-05-24 17:34                             ` Brian Inglis
2017-05-24 18:06                             ` Achim Gratz [this message]
2017-05-24 18:13                       ` Achim Gratz
2017-05-25  0:16                         ` Brian Inglis
2017-05-25  2:07                           ` Doug Henderson
2017-05-25  3:37                             ` Brian Inglis
2017-04-27 17:28   ` [ITA] units Andrew Schulman

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=8760gq5dv1.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).