All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] buildhistory.bbclass: Improve robustness in image file listing
Date: Tue, 28 Jan 2014 11:33:27 +0000	[thread overview]
Message-ID: <1390908807.21652.87.camel@ted> (raw)
In-Reply-To: <CAP9ODKoD9kif9pGiZyf-P2aKpbMFTUM8c2XUg7QUSZi5+BKnaA@mail.gmail.com>

On Mon, 2014-01-27 at 23:52 -0200, Otavio Salvador wrote:
> On Mon, Jan 27, 2014 at 7:52 PM, Randy MacLeod
> <randy.macleod@windriver.com> wrote:
> > On 14-01-23 07:11 AM, Otavio Salvador wrote:
> >>
> >> The filenames sometimes may have strange names. With the 'awk' script
> >> it handled a limited number of spaces in the filename and a package
> >> installing a file named "test file with spaces" would have its name
> >> truncated.
> >>
> >> This patch uses the find's printf formating to simplify the code and
> >> proper handle this case. From a testing image, the only diff produced
> >
> > s/proper/properly/
> >   Yes, I'm with the grammar police; we're here to be helpful.
> >
> >> is:
> >>
> >> ,----[ files-in-image.txt diff ]
> >> | --rwxr-xr-x root       root                0 ./usr/bin/test\ file\ with\
> >> | +-rwxr-xr-x root       root                0 ./usr/bin/test file with
> >> spaces
> >> `----
> >>
> >> The options used are available since findutils 4.2.5, released in 19
> >> Nov 2004, making it available in all supported host distributions.
> >
> >
> > Acked-by: Randy MacLeod <Randy.MacLeod@windriver.com>
> >
> > Works for me, even on CentOS/RHEL-5.9/10 which does indeed have
> > findutils > 4.2.5:
> >
> > $ rpm -qf `which find`
> > findutils-4.2.27-6.el5
> >
> > and the find command seems to work as intended:
> >
> >  $ find jj -printf "%M %-10u %-10g %10s %p -> %l\n"  | cut -c 44-
> >  jj ->
> >  jj/usr ->
> >  jj/usr/bin ->
> >  jj/usr/bin/test file with spaces ->
> 
> Richard, do you want me to send a v2 or can you fix the typo when applying it?

I fixed this one up and merged it.

Cheers,

Richard



  reply	other threads:[~2014-01-28 11:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 12:11 [PATCH] buildhistory.bbclass: Improve robustness in image file listing Otavio Salvador
2014-01-27 18:15 ` Otavio Salvador
2014-01-27 21:52 ` Randy MacLeod
2014-01-28  1:52   ` Otavio Salvador
2014-01-28 11:33     ` Richard Purdie [this message]
2014-01-28  8:59   ` Paul Eggleton
2014-01-28  9:19     ` Phil Blundell
2014-01-28  9:34       ` Paul Eggleton

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=1390908807.21652.87.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.