Greetings All & Good Morning from Au.
I'm currently using the SVN 1.2 TortoiseSVN client (upgraded a few days
ago), and noted the following dates in modules/ssl -
ssl_expr_parse.h 12/11/04
ssl_expr_parse.c 12/02/05
ssl_expr_parse.y 15/06/05
ssl_expr_scan.c 5/02/05
ssl_expr_scan.l 15/06/05
From this it is hardly surprising that yacc is wanted to run. However,
by deleting the above files and running the SVN client again, all the
above files are replaced and given todays date and time, and hence I
suspect Make will be happy enough to live without yacc.
No idea what the 'default' was on the previous TortoiseSVN client but
the present release sets the local file date/time as 'local' but has the
option to set it to 'last commit time'... if I set the flag, then the
dates are pretty much restored as noted above.
HTH,
Norm
Sander Striker wrote:
William A. Rowe, Jr. wrote:
At 09:59 AM 6/16/2005, Sander Striker wrote:
William A. Rowe, Jr. wrote:
* The most recent tarballs have been pulled together with SVN's
absolutely bogus default of [miscellany] use-commit-times = no
(see your ~/.svn/config, where you can uncomment this section
and option).
Bill, I wish you would stop calling things bogus without doing the
research why this is the default.
That's reasonable; does anyone want to point me to the thread
that justified this as the best-choice default? [I suspect I
asked about this once before.]
I remember it was a long one, but I don't have a pointer handy
at this point.
Back to httpd land; the question is --- is this the right choice
for *our tarballs*? Which may or may not be related to the question
above. In any case; this is useful metadata even for end users who
build the package for the reasons I mentioned; does anyone have
a desire/justification to lose the commit dates and use the RM's
checkout date?
Note that the scripts use svn export. IIRC that does default to use
the last commit time, but I could be wrong.
Sander
.
