From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] pkg-infra/show-info: dump install_{staging, target} info
Date: Sat, 3 Aug 2019 08:32:36 +0200 [thread overview]
Message-ID: <20190803063236.GA28984@scaer> (raw)
In-Reply-To: <41428ed5-ed81-067a-829c-00b3e2bdc3ab@mind.be>
Arnout, Vadim, All,
On 2019-08-02 22:43 +0200, Arnout Vandecappelle spake thusly:
> On 02/08/2019 22:42, Arnout Vandecappelle wrote:
> > On 31/07/2019 17:32, Vadim Kochan wrote:
> >> provide info if the package will be installed to staging/target
> >> destinations. Might be useful for analyzing the packages which
> >> installed only for target/staging.
> >>
> >> Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
> >> ---
> >> v2:
> >> 1) use oneliner 'if' to dump install_{staging,target} properties
> >>
> >> v3:
> >> 1) fix evaluation of true/false value via 'subst' (suggested by Yann E. Morin)
> >>
> >> package/pkg-utils.mk | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/package/pkg-utils.mk b/package/pkg-utils.mk
> >> index b7280e930f..ffe198e242 100644
> >> --- a/package/pkg-utils.mk
> >> +++ b/package/pkg-utils.mk
> >> @@ -94,6 +94,8 @@ endef
> >> define _json-info-pkg-details
> >> "version": "$($(1)_DL_VERSION)",
> >> "licenses": "$($(1)_LICENSE)",
> >> + "install-target": $(if $(subst NO,,$($(1)_INSTALL_TARGET)),true,false),
> >> + "install-staging": $(if $(subst NO,,$($(1)_INSTALL_STAGING)),true,false),
>
> Oh, also, someone commented that you should keep install_staging with
> underscore because we already have reverse_dependencies.
And install_target too, of course.
And please also introduce install_images.
Regards,
Yann E. MORIN.
> Regards,
> Arnout
>
> >
> > I still find this ugly.
> >
> > Could you instead add a macro that does something like
> > $(subst NO,false,$(subst YES,true,$(1)))
> > and use that?
> >
> > It may also be handy in other situations.
> >
> > I'm not sure what to call it, maybe bool-to-json or yesno-to-bool
> >
> > Regards,
> > Arnout
> >
> >> "downloads": [
> >> $(foreach dl,$(sort $($(1)_ALL_DOWNLOADS)),
> >> {
> >>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-08-03 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 15:32 [Buildroot] [PATCH v3 1/1] pkg-infra/show-info: dump install_{staging, target} info Vadim Kochan
2019-08-02 20:42 ` Arnout Vandecappelle
2019-08-02 20:43 ` Arnout Vandecappelle
2019-08-03 6:32 ` Yann E. MORIN [this message]
2019-08-06 8:51 ` Vadim Kochan
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=20190803063236.GA28984@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 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.