From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup 0/3] Setup replacement for incver_ifdep
Date: Tue, 22 Sep 2015 17:33:00 -0000 [thread overview]
Message-ID: <87mvwegy0r.fsf@Rainer.invalid> (raw)
In-Reply-To: <1442937170-17580-1-git-send-email-jon.turney@dronecode.org.uk> (Jon Turney's message of "Tue, 22 Sep 2015 16:52:47 +0100")
Jon Turney writes:
> This is an attempt at a setup feature which will allow the removal of the final
> use of 'incver_ifdep' in setup.hint, by _update-info-dir package.
The easiest way to go about this would be to have _update-info-dir
install a perpetual postinstall script that does the very same things it
does now. I'm not even sure it's worth the trouble to try to exit early
if there's nothing to do.
> See the discussions starting at around [1],[2] and following, although this
> takes a slightly different approach.
>
> To be clear: IMHO, this functionality doesn't belong in upset or setup.
Yes, it seems odd to hardcode things that way.
> Since we now have scripts which run on every setup run, a package which requires
> another package to do some work after it is installed or uninstalled can create
> a file to act as a trigger for that to happen.
There aren't any stratified scripts for pre-remove, so a lot of the
things that you might wish for don't work anyway. So again it would
need to be fixed without getting a trigger or setup would need to be
made a lot smarter than it is today.
> Unfortunately, it's not very practical to change to doing that for the all
> packages which contain info files, so I am suggesting this approach.
So just do it unconditionally; I was planning to change _update-info-dir
accordingly, but haven't found the time yet. I do the same with mandb
locally already and I haven't looked back.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2015-09-22 17:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 15:53 Jon Turney
2015-09-22 15:53 ` [PATCH setup 2/3] Remove unfinished, unused support for 'autodep:' lines in setup.ini Jon Turney
2015-09-22 15:53 ` [PATCH setup 3/3] Add support for 'trigger:' " Jon Turney
2015-09-22 15:54 ` [PATCH setup 1/3] Remove unused regex code Jon Turney
2015-09-22 17:33 ` Achim Gratz [this message]
2015-09-23 17:17 ` [PATCH setup 0/3] Setup replacement for incver_ifdep Jon Turney
2015-09-23 18:09 ` Achim Gratz
2015-10-12 13:16 ` Jon Turney
2015-10-12 17:38 ` Achim Gratz
2015-10-15 13:18 ` Jon Turney
2015-10-15 18:01 ` Achim Gratz
2015-10-19 15:41 ` Corinna Vinschen
2015-10-19 17:21 ` Achim Gratz
2015-10-20 10:21 ` Corinna Vinschen
2015-11-23 15:14 ` Jon Turney
2015-11-23 18:54 ` Achim Gratz
2015-11-24 16:59 ` Jon Turney
2015-11-24 18:44 ` Achim Gratz
2015-11-26 10:11 ` Corinna Vinschen
2015-11-26 18:12 ` Achim Gratz
2016-01-28 17:33 ` Jon Turney
2016-01-28 18:06 ` Achim Gratz
2016-01-28 18:41 ` [GOLDSTAR] " Corinna Vinschen
2016-01-29 16:37 ` Andrew Schulman
2016-01-28 18:42 ` Ken Brown
2016-01-28 20:06 ` Eric Blake
2016-01-28 20:17 ` Ken Brown
2016-01-28 20:22 ` Eric Blake
2016-01-29 14:22 ` Jon Turney
2016-01-29 14:53 ` Ken Brown
2016-01-29 19:17 ` Achim Gratz
2016-01-29 21:34 ` Ken Brown
2016-02-06 14:29 ` Ken Brown
2016-02-06 15:31 ` Jon Turney
2016-02-06 15:52 ` Jon Turney
2015-11-23 15:14 ` Jon Turney
2015-10-19 15:33 ` [GOLDSTAR] " Corinna Vinschen
2015-10-19 21:06 ` 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=87mvwegy0r.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).