Nut upsdev - Feb 2010 - 2.4.2 freeze

If nobody objects within 24 hours, I will tag and release 2.4.2-pre1.

cheers,
Arnaud

On Thu, 11 Feb 2010, Arnaud Quette wrote:
> If nobody objects within 24 hours, I will tag and release 2.4.2-pre1.
> 
> cheers,
> Arnaud
For those of us new to svn, could someone list the commands to pull
the code that will be 2.4.2-pre1 so I can test the right bits on Solaris.

Thanks.

-- 
Tim Rice				Multitalents	(707) 887-1469
tim at multitalents.net

Citeren Arnaud Quette <aquette.dev op gmail.com>:
> If nobody objects within 24 hours, I will tag and release 2.4.2-pre1.
Do we really need tags for this? In recent history, we have seen  
little to no responses to the -pre releases. Can't we just direct  
people to a specific SVN revision? Or even better, provide them with a  
link to a tarball that they can use?

Best regards, Arjen
-- 
Please keep list traffic on the list

Citeren Tim Rice <tim op multitalents.net>:
> r2353 looks good on UnixWare 7.1.4, OpenServer 6, & Solaris 10 all with
> native compilers.
Thanks for reporting this.
> UnixWare 7.1.1 chokes on __func__
> ....
> UX:acomp: ERROR: "/opt/src/utils/nut-2.4.1-r2353/common/state.c",
> line 105: undefined symbol: __func__
> ....
This is something that was introduced in C99 so I'm not too surprised  
this doesn't work on older systems. Is this the native compiler from  
UnixWare 7.1.1?
> That's just a FYI. I would not hold up release for this.
> UnixWare 7.1.1 is not a currently shipping system.
We can easily work around this through some autoconf magic, so I see  
no reason why we shouldn't attempt to support this. It is probably  
better to make the debugging output (a little) harder to interpret,  
than to fail building at all.

Best regards, Arjen
-- 
Please keep list traffic on the list