Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] grep-2.5.1a: fix grep for LSB compliance
Date: Tue, 27 Aug 2013 11:43:39 +0100	[thread overview]
Message-ID: <1377600219.5452.60.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <521BFA2A.4090508@linux.intel.com>

On Mon, 2013-08-26 at 18:00 -0700, Saul Wold wrote:
> On 08/27/2013 02:43 AM, Li Zhijian wrote:
> > add patch from grep-2.5.1-55.el5.src.rpm and
> > enable configration option of --without-include-regex
> >
> > LSB core-tests failed at /tset/LI18NUX2K.L1/utils/grep-tp/T.grep-tp 5,T.egrep-tp 5
> > which is intend to verify this utility can perform pattern matching in searches
> > without regard to case if -i option is specified.
> >
> > Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> >   SRC_URI = "${GNU_MIRROR}/grep/grep-${PV}.tar.bz2 \
> >              file://uclibc-fix.patch \
> > @@ -13,8 +13,25 @@ SRC_URI = "${GNU_MIRROR}/grep/grep-${PV}.tar.bz2 \
> >              file://gettext.patch \
> >              file://fix64-int-to-pointer.patch \
> >              file://Makevars \
> > -           file://grep-CVE-2012-5667.patch \
> 
> Why are you removing this patch?

He didn't actually remove it, he just moved it further down the list.
But...

> >              file://fix-for-texinfo-5.1.patch \
> > +           file://grep-2.5.1-fgrep.patch \
> > +           file://grep-2.5.1-bracket.patch \
> > +           file://grep-2.5-i18n.patch \
> > +           file://grep-2.5.1-oi.patch \
> > +           file://grep-2.5.1-manpage.patch \
> > +           file://grep-2.5.1-color.patch \
> > +           file://grep-2.5.1-icolor.patch \
> > +           file://grep-skip.patch \
> > +           file://grep-2.5.1-egf-speedup.patch \
> > +           file://grep-2.5.1-dfa-optional.patch \
> > +           file://grep-2.5.1-tests.patch \
> > +           file://grep-2.5.1-w.patch \
> > +           file://grep-P.patch \
> > +           file://grep-CVE-2012-5667.patch \
> > +           file://grep-empty-pattern.patch \
> > +           file://grep-bz460641.patch \
> > +           file://grep-bz434934.patch \
> > +           file://grep-man-label.patch \

... it's fairly hard to believe that all these patches are really
necessary to fix the problem with "grep -i" that's described in the
checkin message.  It looks as though a more accurate description of this
change would be something like "grep-2.5.1a: import all patches from
RHEL".

Also, although adding --without-included-regex probably is a good thing
(and probably ought to be done for grep-2.14 as well) it's not very
obvious that this has anything to do with the LSB fix either.

p.




  parent reply	other threads:[~2013-08-27 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  9:43 [PATCH] grep-2.5.1a: fix grep for LSB compliance Li Zhijian
2013-08-27  1:00 ` Saul Wold
2013-08-27  4:32   ` Li Zhijian
2013-08-27  6:52     ` Saul Wold
2013-08-28  6:16       ` Li Zhijian
2013-08-27 10:43   ` Phil Blundell [this message]
2013-08-28  5:47     ` Li Zhijian

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=1377600219.5452.60.camel@phil-desktop.brightsign \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox