From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup 0/3] Setup replacement for incver_ifdep
Date: Mon, 19 Oct 2015 15:41:00 -0000 [thread overview]
Message-ID: <20151019154100.GB18989@calimero.vinschen.de> (raw)
In-Reply-To: <87oag0qad3.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 1977 bytes --]
On Oct 15 20:01, Achim Gratz wrote:
> Jon Turney writes:
> >> I still don't think the triggers should be implemented or at least not
> >> in the way you've been proposing.
> >
> > Can you explain the reason why?
>
> Triggers need to be coordinated among packages and we currently don't
> have an infrastructure for that. And implementing just a single trigger
> for info files is special-casing this thing too much.
>
> > I think that's more or less what I implemented.
>
> I'm talking about doing it with a perpetual postinstall script.
>
> >> But it would be possible to just add /
> >> remove the corresponding entries with a bit more bookkeeping. I'll try
> >> something of that, but not immediately.
> >
> > I guess that list of matching files added/removed could be written
> > into or associated with the trigger file, but the benefit starts to
> > look a bit marginal, (especially as this is not intended as a general
> > solution, but only for use with _update-info-dir, and other future
> > package-to-package triggers are written directly in the packages
> > themselves)
>
> Again, I don't see why updating the info dir should be so special, it
> can be done in postinstall without getting special-cased in setup:
I agree. Actually, considering that the info files are stored in just a
single well-known directory, /usr/share/info(*), and further considering
that updated files are rewritten when overwritten, shouldn't it be entirely
sufficient if the update_info_dir script performs a simple test like this:
- Does /usr/share/info/dirs exist?
No -> run install-info
Yes -> Is /usr/share/info/dirs mtime < /usr/share/info mtime?
No -> Do nothing
Yes -> run install-info
?
(*) We should drop the check for /usr/info, imho.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-19 15:41 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 3/3] Add support for 'trigger:' lines in setup.ini Jon Turney
2015-09-22 15:53 ` [PATCH setup 2/3] Remove unfinished, unused support for 'autodep:' " Jon Turney
2015-09-22 15:54 ` [PATCH setup 1/3] Remove unused regex code Jon Turney
2015-09-22 17:33 ` [PATCH setup 0/3] Setup replacement for incver_ifdep Achim Gratz
2015-09-23 17:17 ` 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 [this message]
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=20151019154100.GB18989@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).