Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] spport/check-bin-arch: accept arbitrary ignore paths
Date: Wed, 7 Mar 2018 22:22:59 +0100	[thread overview]
Message-ID: <20180307212259.GC2578@scaer> (raw)
In-Reply-To: <87a7vjobry.fsf@dell.be.48ers.dk>

Peter, All,

On 2018-03-07 21:45 +0100, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
[--SNIP--]
>  > +* +LIBFOO_BIN_ARCH_EXCLUDE+ is a space-separated list of path (relative
> s/path/paths/
> > +  to the target directory) to ignore when checking that the package
>  > +  installs correctly cross-compiled binaries. You seldom need to set this
>  > +  variable, unless the package installs installs binary blobs in the
> s/installs installs/installs/

Typoes fixed.

>  > +  non-default locations: `/lib/firmware`, `/usr/lib/firmware`,
>  > +  `/lib/modules`, and `/usr/share`.
> 
> This sounds a bit confusing to me, E.G. like these are non default
> locations.
> 
> Perhaps we should instead write:
> 
> variable, unless the package installs binary blobs outside the default
> locations, which are `/lib/firmware`, `/usr/lib/firmware`,
> `/lib/modules` and '/usr/share`, as these locations are automatically
> excluded.

Indeed, it was not clear (except maybe just in my twisted head). I've
rephrased slightly differently from your suggestion, but if you don;t
like it, we can go with yours instead.

>  >  if test -z "${package}" -o -z "${pkg_list}" -o -z "${readelf}" -o -z "${arch_name}" ; then
>  > -	echo "Usage: $0 -p <pkg> -l <pkg-file-list> -r <readelf> -a <arch name>"
>  > +	echo "Usage: $0 -p <pkg> -l <pkg-file-list> -r <readelf> -a <arch name> [-i PATTERN ...]"
> 
> We don't really document this as a pattern (even if it gets passed to ~=
> in the end), so perhaps it would be clearer to say [ -i PATH ]?

ACK.

> Otherwise it looks good to me, thanks!

Thanks! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-03-07 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 20:27 [Buildroot] [PATCH 0/2] support/check-bin-arch: add support for excluding arbitrary locations Yann E. MORIN
2018-03-07 20:27 ` [Buildroot] [PATCH 1/2] spport/check-bin-arch: accept arbitrary ignore paths Yann E. MORIN
2018-03-07 20:45   ` Peter Korsgaard
2018-03-07 21:22     ` Yann E. MORIN [this message]
2018-03-07 20:27 ` [Buildroot] [PATCH 2/2] support/check-bin-arch: exclude kernel modules for merged /usr Yann E. MORIN
2018-03-07 20:45   ` Peter Korsgaard
2018-03-07 21:23     ` Yann E. MORIN
2018-03-07 21:35       ` Peter Korsgaard

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=20180307212259.GC2578@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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