Re: [blfs-dev] A couple of command inconsistencies
Yes, those points've already been made in your first post, understood, and addressed in the reply: IOW, you might want to use e.g.: -e 's/\(.*\)[[:blank:]]*$/\1/' or even -e 's/\(.*\)[[:blank:]]*[[:blank:]]*$/\1/' or similar, depending on details of the processing environment - e.g. you might need/want sed's '-r' flag also, /or change the '[[:blank:]]' to '[ \t]' (that first char is a single (horizontal-)space char) or to '[]' (a single horiz-space char and a single tab-char), c. Well rather and try and deal with all possible chars after the , I've added the blank to my script for iptables and ruby. If the editors decide to add more spaces, or a tab or whatever after a , my script will fail and then I can try and fix it. No loss of life will ensue so 'suck it and see' is a good approach for this problem. jb. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] A couple of command inconsistencies
From: John Burrell john_burr...@hotmail.com To: BLFS Development List blfs-dev@lists.linuxfromscratch.org Date: Mon, 7 Jul 2014 15:24:46 + Subject: Re: [blfs-dev] A couple of command inconsistencies Yes, those points've already been made in your first post, understood, and addressed in the reply: IOW, you might want to use e.g.: -e 's/\(.*\)[[:blank:]]*$/\1/' or even -e 's/\(.*\)[[:blank:]]*[[:blank:]]*$/\1/' or similar, depending on details of the processing environment - e.g. you might need/want sed's '-r' flag also, /or change the '[[:blank:]]' to '[ \t]' (that first char is a single (horizontal-)space char) or to '[ ]' (a single horiz-space char and a single tab-char), c. Well rather and try and deal with all possible chars after the , I've added the blank to my script for iptables and ruby. If the editors decide to add more spaces, or a tab or whatever after a , my script will fail and then I can try and fix it. - but the '[[:blank:]]*' (without the quotes, obviously) deals with the 'problem' once for all: why would one spend the time to add just a blank to the sed, rather than add the regex ... . But, it's your script, of course. No loss of life will ensue so 'suck it and see' is a good approach for this problem. (Maybe not loss of life, but perhaps loss/waste of time... .) rgds, akh jb. -- -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] A couple of command inconsistencies
John Burrell wrote: Dear Editors In the BLFS commands postlfs, 041-iptables has this line --enable-libipq There is a space after the which makes it difficult to do a global delete on the This is also true for general/251-ruby with this line: --docdir=/usr/share/doc/ruby-2.1.2 Would you kindly remove the space after the for these two commands to make them consistent with all the other commands in the xml files. OK, but I don't know why you would have the problem you describe. Bruce - while I remember: apache-ant-1.9.4-src.tar.bz2 is missing from http://anduin.linuxfromscratch.org/sources/BLFS/svn/a/ and opal-3.10.10.tar.xz is missing from http://anduin.linuxfromscratch.org/sources/BLFS/svn/o/ Updated on the master. It will be 12 hours or so for anduin to update. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] A couple of command inconsistencies
From: John Burrell john_burr...@hotmail.com To: blfs-...@linuxfromscratch.org blfs-...@linuxfromscratch.org Date: Sun, 6 Jul 2014 20:33:55 + Subject: [blfs-dev] A couple of command inconsistencies Dear Editors In the BLFS commands postlfs, 041-iptables has this line --enable-libipq There is a space after the which makes it difficult to do a global delete on the This is also true for general/251-ruby with this line: --docdir=/usr/share/doc/ruby-2.1.2 Would you kindly remove the space after the for these two commands to make them consistent with all the other commands in the xml files. . . While yes, it's good to have consistency in xml source, a processing of that source should really be 'liberal in what it accepts' as input, at least insofar as allowing for the possibility of such spaces, surely? You could e.g. match on a regex such as '[[:blank:]]*$' or similar (depending on what the processing environment will accept regex-wise). rgds, akh -- -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] A couple of command inconsistencies
Dear Editors In the BLFS commands postlfs, 041-iptables has this line --enable-libipq There is a space after the which makes it difficult to do a global delete on the This is also true for general/251-ruby with this line: --docdir=/usr/share/doc/ruby-2.1.2 Would you kindly remove the space after the for these two commands to make them consistent with all the other commands in the xml files. . . While yes, it's good to have consistency in xml source, a processing of that source should really be 'liberal in what it accepts' as input, at least insofar as allowing for the possibility of such spaces, surely? You could e.g. match on a regex such as '[[:blank:]]*$' or similar (depending on what the processing environment will accept regex-wise). I wrote a script to build the scripts to install the packages for each section of BLFS (I was tempted to write after that sentence 'That lay in the house that Jack built' but managed to stop myself!). I install as a package user so I want to keep the configure, make and install logs. This means removing all the from the end of the command lines. I use a sed to do this: -e 's/\(.*\)$/\1/' If the command ends in this works fine. If it ends in a space it doesn't and leaves the in place, which then causes the script to fail. I've only found the two lines noted above that have such a space. To me the space seems superfluous. jb. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
