Le 25 oct. 06 à 18:04, Stepan Kasal a écrit :
Hello,
On Wed, Oct 25, 2006 at 05:35:31PM +0200, Akim Demaille wrote:
find stampfile -newer $file
indeed, according to the documentation, the predicate is true if
stampfile is strictly newer than $file. So the implementation would
have to be s
Hello,
On Wed, Oct 25, 2006 at 05:35:31PM +0200, Akim Demaille wrote:
> > find stampfile -newer $file
indeed, according to the documentation, the predicate is true if
stampfile is strictly newer than $file. So the implementation would
have to be something like:
# is_younger FILE FILES
# --
Certainly. But frequently in Automake tests the problem is as
follows:
do_something with $file
$sleep
touch stampfile
do_something_else with $file
ensure that $file is updated/not updated.
If the last command is done with `ls -1t', I either have to think
about
the locale ordering
> * Akim Demaille wrote on Mon, Oct 23, 2006 at 07:20:38AM CEST:
> > Do you know of any means to compute the list of files with *equal*
> > time stamp? Hum, playing with repetitive calls to find -not -newer
> > should do that,
Erm. `find -not' is not POSIX, but `find !' is.
* Akim Demaille wrote on Mon, Oct 23, 2006 at 07:20:38AM CEST:
> >>>I have some problems with these definitions. If there are several
> >>>files that have the youngest time stamp, then the order depends on
> >>>the locale.
> >>
> >>Nia? How can the locale change the order to time stamps?
> >
> >
I have some problems with these definitions. If there are several
files that have the youngest time stamp, then the order depends on
the locale.
Nia? How can the locale change the order to time stamps?
Only if the time stamps are the same:
$ touch a B
$ LC_ALL=C ls -1t
B
a
$ ls -1t
a
B
$ l
* Akim Demaille wrote on Sun, Oct 22, 2006 at 07:10:20PM CEST:
>
> >
> >>+ then
> >>+ # No need to copy, that's the same file.
> >>+ continue
> >>+ else :; fi } &&
> >
> >There has to be a semicolon before the }, I think.
>
> I don't you do: I think the semi-colon is required to end
I think using \ then newline then && was done to mimic GCS style for C
code. FWIW, I prefer your style as well.
That style was also used elsewhere.
Wouldn't using $diffprog without double quotes be more consistent,
so the user could pass options to diff as well?
Sure.
+test x"
Hello Akim,
A quick review of your patch, completely untested.
> from Akim Demaille <[EMAIL PROTECTED]>
[...]
> Don't use '\' to continue commands: && suffices.
I think using \ then newline then && was done to mimic GCS style for C
code. FWIW, I prefer your style as well.
> --- NEWS 1
