public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Jacob Kroon <jacob.kroon@gmail.com>
To: Ross Burton <ross.burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"schnitzeltony@gmail.com" <schnitzeltony@gmail.com>
Subject: Re: [OE-core] [PATCH] libxml2: don't override XML_CATALOG_FILES in xmllint wrapper if already set
Date: Fri, 9 Sep 2022 19:05:24 +0200	[thread overview]
Message-ID: <890e5f59-6541-8e87-c57e-f448f444d631@gmail.com> (raw)
In-Reply-To: <8B8690ED-C7A3-4CC4-9D37-1BC5397DCA4C@arm.com>

On 9/9/22 19:00, Ross Burton wrote:
>>>   -	create_wrapper ${D}${bindir}/xmllint XML_CATALOG_FILES=${sysconfdir}/xml/catalog
>>> +	create_wrapper ${D}${bindir}/xmllint 'XML_CATALOG_FILES=${XML_CATALOG_FILES:-${sysconfdir}/xml/catalog}'
>>
>> That ...:-${sysconfdir}/... looks odd. Is that hyphen intentional ?
> 
> Yes:
> 
>       ${parameter:-word}    Use Default Values.  If parameter is unset or null, the expansion of word is substituted; otherwise, the value of
>                             parameter is substituted.
> 
> Ross
> 

Aha, very nice, sorry for the noise.

Jacob


  reply	other threads:[~2022-09-09 17:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 16:36 [PATCH] libxml2: don't override XML_CATALOG_FILES in xmllint wrapper if already set Ross Burton
2022-09-09 16:53 ` [OE-core] " Jacob Kroon
2022-09-09 17:00   ` Ross Burton
2022-09-09 17:05     ` Jacob Kroon [this message]
2022-09-09 22:54 ` Richard Purdie
     [not found] ` <17135317F9CABC3C.4025@lists.openembedded.org>
2022-09-11 22:21   ` Richard Purdie
     [not found]   ` <1713EE7A59F012D9.1776@lists.openembedded.org>
2022-09-12  9:43     ` Richard Purdie
2022-09-12 21:59       ` Andreas Müller
2022-09-13 17:14       ` Peter Kjellerstedt

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=890e5f59-6541-8e87-c57e-f448f444d631@gmail.com \
    --to=jacob.kroon@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.com \
    --cc=schnitzeltony@gmail.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