From: "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
Saul Wold <sgw@linux.intel.com>
Cc: "Eggleton, Paul" <paul.eggleton@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] populate_sdk_base: ensure that filenames with empty space character are handled
Date: Sat, 12 Jul 2014 10:20:47 -0300 [thread overview]
Message-ID: <53C1362F.9040006@gmail.com> (raw)
In-Reply-To: <CAP9ODKpMVXway08KT0R+uyLr6V37ouCa038t_n-LzSOdDQ6h=g@mail.gmail.com>
Hi Otavio
Em 08-07-2014 22:33, Otavio Salvador escreveu:
> Now talking about the patch itself, Joao, did you try to avoid the
> extra fork calling echo? Using '-print0' option in find might help.
Not until now. But I agree about your concern. So, instead of
executable_files=$($SUDO_EXEC find $native_sysroot -type f -perm /111
-exec echo \'{}\' \;)
Its better do:
executable_files=$($SUDO_EXEC find $native_sysroot -type f -perm /111
-printf "'%h/%f' ")
No extra fork was used with -printf "'%h/%f' ".
The argument -print0 is not an option because the output of find command
will be 'path1 path2 path 3' a concatenation of strings not strings
split by space and protected with ' '.
Both results are valid. But the second is nicer. What do you think?
When I did this patch I was not thinking to solve all problems about
spaces in filename. However a deep dig is needed to track all points
that have this issue.
Thanks.
--
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
next prev parent reply other threads:[~2014-07-12 13:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 1:58 [PATCH 0/2] add nativesdk to BBCLASSEXTEND to python-distribute and to fix the side effect of it João Henrique Ferreira de Freitas
2014-07-02 1:58 ` [PATCH 1/2] python-distribute: add nativesdk to BBCLASSEXTEND João Henrique Ferreira de Freitas
2014-07-02 1:58 ` [PATCH 2/2] populate_sdk_base: ensure that filenames with empty space character are handled João Henrique Ferreira de Freitas
2014-07-09 0:19 ` Saul Wold
2014-07-09 1:33 ` Otavio Salvador
2014-07-12 13:20 ` João Henrique Ferreira de Freitas [this message]
2014-07-14 15:10 ` Otavio Salvador
2014-07-14 22:55 ` [PATCH v2 0/2] add nativesdk to BBCLASSEXTEND to python-distribute and to fix the side effect of it João Henrique Ferreira de Freitas
2014-07-14 22:55 ` [PATCH v2 1/2] python-distribute: add nativesdk to BBCLASSEXTEND João Henrique Ferreira de Freitas
2014-07-15 13:35 ` Otavio Salvador
2014-07-17 0:50 ` João Henrique Ferreira de Freitas
2014-07-17 11:33 ` Otavio Salvador
2014-07-14 22:55 ` [PATCH v2 2/2] populate_sdk_base: ensure that filenames with empty space character are handled João Henrique Ferreira de Freitas
2014-07-15 13:33 ` Otavio Salvador
2014-07-16 3:01 ` João Henrique Ferreira de Freitas
2014-07-18 3:09 ` [PATCH v3 0/2] add nativesdk to BBCLASSEXTEND to python-distribute and to fix the side effect of it João Henrique Ferreira de Freitas
2014-07-18 3:09 ` [PATCH v3 1/2] python-distribute: add nativesdk to BBCLASSEXTEND João Henrique Ferreira de Freitas
2014-07-18 3:09 ` [PATCH v3 2/2] populate_sdk_base: ensure that filenames with empty space character are handled João Henrique Ferreira de Freitas
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=53C1362F.9040006@gmail.com \
--to=joaohf@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=paul.eggleton@linux.intel.com \
--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