Re: [log4perl-devel] Re: FAIL Log-Log4perl-0.28 sun4-solaris 2.8

[Kevin G. <ke...@go...>]

Msc...@ao... wrote:
 >> Problem is that the CPAN release needs a new version number.
 >
 > Never mind, I got confused :). I've just release 0.29 to the web
 > site, based on your branch.


There ya go!  That's what I was getting at.

What was the final disposition of the 017Watch.t test?   My position 
would be that if we can't trust the timestamps on the filesystem, the 
whole init_and_watch system is going to break down.  We wouldn't be able 
to do
	if ( ($LAST_CHECKED_AT + $WATCH_DELAY) < time()){

because there's no relation between time() and stat($FILE_TO_WATCH). 
Instead of calling time(), you'd have to touch a file on the filesystem, 
in effect asking the filesystem what time *it* thinks it is now.

So I think we should leave 036JSyslog.t as it is.  Drifing times on an 
NFS mount should actually cause a failure (they'll bollix other things 
to, like tar for instance--ntp synchronization is a very good idea for 
NFS situations ).

And what was the final disposition of 036JSyslog.t?  I just changed it 
to always succeed.  That way it won't keep log4perl from installing, but 
it will give some indication to the user whether they can expecte syslog 
logging to work on their system.  I just did that right now, so you'll 
need to update the web site (you didn't send to cpan yet, right?)

 > Please verify and merge your stuff to the
 > tip.

Done!  But I'll wait till the end of the day to check it in.

-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217