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: [PATCH setup 0/3] Setup replacement for incver_ifdep
Date: Mon, 19 Oct 2015 17:21:00 -0000	[thread overview]
Message-ID: <87io62hiz6.fsf@Rainer.invalid> (raw)
In-Reply-To: <20151019154100.GB18989@calimero.vinschen.de> (Corinna Vinschen's	message of "Mon, 19 Oct 2015 17:41:00 +0200")

Corinna Vinschen writes:
> 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

Can this be relied on for all possible file systems?

Otherwise, as I said, the same general algorithm as used for autorebase
would be workable.  It might in fact be possible to sneak that into the
rebaselst generation since the information is already passing by.


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

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

  reply	other threads:[~2015-10-19 17:21 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 ` [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
2015-10-19 17:21           ` Achim Gratz [this message]
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=87io62hiz6.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).