LCDproc development and user support list

Text archives Help

[Lcdproc] Release 0.5.1 ?

Chronological Thread 
  • From: rkrayer AT (Russell Krayer)
  • Subject: [Lcdproc] Release 0.5.1 ?
  • Date: Tue Sep 19 04:08:02 2006

Hi Peter,

>From: Peter Marschall
><peter AT>
>lcdproc AT
>Subject: Re: [Lcdproc] Release 0.5.1 ?
>Date: Mon, 18 Sep 2006 21:26:58 +0200
>Hi Jannis, hi list,
>On Monday, 18. September 2006 18:04, Jannis Achstetter wrote:
> > What about releasing 0.5.1 as there have been nice fixes to some
> > drivers (including the CF-635). I think it would be better for new
> > users to have these devices working with stable code as to tell them
> > they have to checkout CVS.
>I was considering making a pre-announcement of an upcoming LCDproc 0.5.1
>release in the next few days.
>I wanted to wait a few days before the announcement since I did not get any
>feedback regarding the CFONTZ633_WRITE_DELAY issue yet.

I have lcdproc-CVS-current-20060918 with CFONTZ633_WRITE_DELAY=50 running
seemingly flawlessly on my PowerPC-based gentoo box (a kurobox) with gcc

I have one tiny issue with the lcdvc client, it loops forever on getopt()
without this patch (my char seems implicity unsigned or something):

--- lcdvc/lcdvc.c 2003-04-30 19:42:08.000000000 -0400
+++ lcdvc-patched/lcdvc.c 2006-09-14 21:11:30.000000000 -0400
@@ -93,7 +93,7 @@

int process_command_line( int argc, char ** argv )
- char c;
+ int c;
char * p;
int temp_int;
int error = 0;

>In the mean time (i.e. in the last 3 days ;-) I have
>* upgraded the man pages a bit so that they reflext the reality better
>* improved (and documented) the config file parser logic so that it now
> - accepts spaces around keys and values
> - accepts spaces in the section labels
> (might save a few lines in lcdexec.conf ;-)
> - returns failure on parsing errors
> all this while keeping compatibility with the existing config file
>Athough this is not the official announcement of an upcoming 0.5.1 release:
>Please check out tonight's tar ball and test it !
>Please report any failures or bugs you encounter to help shake out
>bugs in CVS and make the upcoming release as good as possible.
>(even better: send patches fixing bugs)

Keep up the good work!

Russ Krayer

Archive powered by MHonArc 2.6.18.

Top of page