From: John Spencer <maillist-lvm@barfooze.de>
To: linux-lvm@redhat.com
Cc: agk@redhat.com
Subject: Re: [linux-lvm] lvm2 portability issues (GNU sed is assumed)
Date: Thu, 31 Jan 2013 04:31:35 +0100 [thread overview]
Message-ID: <5109E597.5040706@barfooze.de> (raw)
In-Reply-To: <20130130025520.GB868@agk-dp.fab.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
On 01/30/2013 03:55 AM, Alasdair G Kergon wrote:
> On Tue, Jan 29, 2013 at 08:51:21PM +0100, John Spencer wrote:
>> may i ask kindly to reformulate that statement so that it works with
>> posix sed (as used in busybox 1.20.2) ?
>
> I'm perfectly happy using modern extensions to these tools:)
>
> If you want this to work with alternative versions, please send a tested
> patch for us to incorporate. (Either modifications to the commands so
> it works with both or else alternative versions which configure chooses
> between.)
a couple of regex experts looked at it, and the reason it didnt work is
simply a bug: the \ before d is wrong. apparently the author meant to
escape the makefile variable that follows, but that is not necessary and
so the backslash gets passed on.
find attached a patch that works correctly with gnu sed and busybox sed.
btw: apparently there are 2 other bugs in that sed statement:
| should become \| to work as intended by the author (gnu sed only), and
[ \*] should become [ *].
but apparently this part of the regex isn't used anyway, so it might be
the best to just remove it.
i left that part unfixed, as it is not crucial, so someone else might
want to look at it.
thanks,
--JS
>
> Alasdair
>
>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-make.tmpl.in-fix-buggy-sed-statement-that-worked-by-.patch --]
[-- Type: text/x-patch; name="0001-make.tmpl.in-fix-buggy-sed-statement-that-worked-by-.patch", Size: 0 bytes --]
next prev parent reply other threads:[~2013-01-31 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 19:51 [linux-lvm] lvm2 portability issues (GNU sed is assumed) John Spencer
2013-01-30 2:55 ` Alasdair G Kergon
2013-01-31 3:31 ` John Spencer [this message]
2013-02-24 15:12 ` John Spencer
2013-03-19 17:38 ` John Spencer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5109E597.5040706@barfooze.de \
--to=maillist-lvm@barfooze.de \
--cc=agk@redhat.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.