From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] italic-man
Date: Sun, 11 Aug 2019 16:17:00 -0000 [thread overview]
Message-ID: <87lfvzy8v6.fsf@Rainer.invalid> (raw)
In-Reply-To: <05f12d5f-3cb8-e331-a7ee-7fa5812218d8@towo.net> (Thomas Wolff's message of "Sun, 11 Aug 2019 11:33:19 +0200")
Thomas Wolff writes:
>> How are updates to man-db, /etc/man_db.conf etc. handled?
> I checked the man-db postinstall script, and it does not overwrite
> man_db.conf if it exists already, so the modification will persist.
No postinstall script should ever modify files in /etc if they have been
changed from their default. By extension, they shouldn't do any editing
there either.
>> Is a permanent postinstall script provided to maintain the conf on man-db updates?
> Not needed under the observation above. If it were, how would a
> permanent postinstall be deployed?
By naming it correctly and making sure it behaves sensibly considering
that it runs each time setup finishes, i.e. exiting as early as possible
if there's nothing to do, using dash instead of bash and a number of
other things.
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
next prev parent reply other threads:[~2019-08-11 16:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 6:01 Thomas Wolff
2019-08-09 12:59 ` Jon Turney
2019-08-09 15:07 ` Ken Brown
2019-08-09 18:56 ` Achim Gratz
2019-08-09 19:31 ` Thomas Wolff
2019-08-09 20:51 ` Brian Inglis
2019-08-10 9:07 ` Thomas Wolff
2019-08-10 21:39 ` Thomas Wolff
2019-08-10 22:29 ` Brian Inglis
2019-08-11 9:33 ` Thomas Wolff
2019-08-11 16:17 ` Achim Gratz [this message]
2023-01-21 17:04 Thomas Wolff
2023-02-16 18:59 ` Jon Turney
2023-02-16 19:17 ` Thomas Wolff
2023-06-21 21:45 ` Thomas Wolff
2023-06-25 13:36 ` Jon Turney
2023-06-25 13:59 ` Thomas Wolff
2023-06-25 16:02 ` ASSI
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=87lfvzy8v6.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).