[ANNOUNCE] VDR developer version 1.3.48

  Oliver Endriss wrote:
> Klaus Schmidinger wrote:
>> VDR developer version 1.3.48 is now available at
>> ...
>> - Simplified the 'grep|awk|sed' command to retrieve the VDR/APIVERSION to a single
>>    'sed' call.
> 
> (1) My sed does not accept lines like this:
> | sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/; p }' config.h
> | sed: -e expression #1, char 47: Extra characters after command
> 
> This works:
> | sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/p; }' config.h
> | 1.3.47
> 
> (2) The newplugin script is broken:
> - references VDRVERSION, not APIVERSION
> - '\' must be escaped
> - sed problem as above

Just to make sure I don't make any stupid last minute error
here's the complete change that resulted from this.
Maybe somebody finds the time to look over this...

Klaus
  

Klaus Schmidinger wrote:
> Just to make sure I don't make any stupid last minute error
> here's the complete change that resulted from this.
> Maybe somebody finds the time to look over this...

I gave everything a test run, seems to work. GNU-sed 4.1.2. Out of 
curiosity, I've tried solaris 5.6 sed of 1997 and AIX 5.2 sed, and they 
accepted it too.

Cheers,

Udo
  

Klaus Schmidinger wrote:
> Oliver Endriss wrote:
>> Klaus Schmidinger wrote:
>>> VDR developer version 1.3.48 is now available at
>>> ...
>>> - Simplified the 'grep|awk|sed' command to retrieve the
>>> VDR/APIVERSION to a single
>>>    'sed' call.
>>
>> (1) My sed does not accept lines like this:
>> | sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/; p }' config.h
>> | sed: -e expression #1, char 47: Extra characters after command
>>
>> This works:
>> | sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/p; }' config.h
>> | 1.3.47
>>
>> (2) The newplugin script is broken:
>> - references VDRVERSION, not APIVERSION
>> - '\' must be escaped
>> - sed problem as above
> 
> Just to make sure I don't make any stupid last minute error
> here's the complete change that resulted from this.
> Maybe somebody finds the time to look over this...
> 
> Klaus
> 

Im trying to test this from the console and I seem to have a problem with the
following command (using sed-4.1.4-7 from debian sid):

 "sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$$/\1/; p }' config.h"

This returns nothing.

 "sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/; p }' config.h"

This returns:

1.3.48

Is that right? Removing one of the "$" seems to fix it..

BR.
  

>>
> 
> Im trying to test this from the console and I seem to have a problem with the
> following command (using sed-4.1.4-7 from debian sid):
> 
>  "sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$$/\1/; p }' config.h"
> 
> This returns nothing.
> 
>  "sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/; p }' config.h"
> 
> This returns:
> 
> 1.3.48
> 
> Is that right? Removing one of the "$" seems to fix it..
> 

Sorry, I meant to say this command returns nothing:

sed -ne '/define VDRVERSION/s/^.*"\(.*\)".*$$/\1/p' config.h

and this command works:

sed -ne '/define VDRVERSION/s/^.*"\(.*\)".*$/\1/p' config.h


BR.
  

C.Y.M wrote:
> Klaus Schmidinger wrote:
>> Oliver Endriss wrote:
>>> Klaus Schmidinger wrote:
>>>> VDR developer version 1.3.48 is now available at
>>>> ...
>>>> - Simplified the 'grep|awk|sed' command to retrieve the
>>>> VDR/APIVERSION to a single
>>>>    'sed' call.
>>> (1) My sed does not accept lines like this:
>>> | sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/; p }' config.h
>>> | sed: -e expression #1, char 47: Extra characters after command
>>>
>>> This works:
>>> | sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/p; }' config.h
>>> | 1.3.47
>>>
>>> (2) The newplugin script is broken:
>>> - references VDRVERSION, not APIVERSION
>>> - '\' must be escaped
>>> - sed problem as above
>> Just to make sure I don't make any stupid last minute error
>> here's the complete change that resulted from this.
>> Maybe somebody finds the time to look over this...
>>
>> Klaus
>>
> 
> Im trying to test this from the console and I seem to have a problem with the
> following command (using sed-4.1.4-7 from debian sid):
> 
>  "sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$$/\1/; p }' config.h"
> 
> This returns nothing.
> 
>  "sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/; p }' config.h"
> 
> This returns:
> 
> 1.3.48
> 
> Is that right? Removing one of the "$" seems to fix it..

That's all right. The '$' needs to be doubled in the Makefile.

Klaus
  

On Tue, Apr 25, 2006 at 11:49:29PM -0700, C.Y.M wrote:
> Klaus Schmidinger wrote:
> > Oliver Endriss wrote:
> >> Klaus Schmidinger wrote:
> >>> VDR developer version 1.3.48 is now available at
> >>> ...
> >>> - Simplified the 'grep|awk|sed' command to retrieve the
> >>> VDR/APIVERSION to a single
> >>>    'sed' call.
> >>
> >> (1) My sed does not accept lines like this:
> >> | sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/; p }' config.h
> >> | sed: -e expression #1, char 47: Extra characters after command
> >>
> >> This works:
> >> | sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/p; }' config.h
> >> | 1.3.47
> >>
> >> (2) The newplugin script is broken:
> >> - references VDRVERSION, not APIVERSION
> >> - '\' must be escaped
> >> - sed problem as above
> > 
> > Just to make sure I don't make any stupid last minute error
> > here's the complete change that resulted from this.
> > Maybe somebody finds the time to look over this...
> > 
> > Klaus
> > 
> 
> Im trying to test this from the console and I seem to have a problem with the
> following command (using sed-4.1.4-7 from debian sid):
> 
>  "sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$$/\1/; p }' config.h"
> 
> This returns nothing.
> 
>  "sed -ne '/define APIVERSION/ { s/^.*"\(.*\)".*$/\1/; p }' config.h"
> 
> This returns:
> 
> 1.3.48
> 
> Is that right? Removing one of the "$" seems to fix it..

Hmm ... within Makefiles the first $ is readed by the make program
and if there is no second $ you'll get the make variable $/ ...

       Werner