public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: "rpjday@crashcourse.ca" <rpjday@crashcourse.ca>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Quentin Schulz <quentin.schulz@streamunlimited.com>,
	OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] couple questions on PACKAGECONFIG (for improving docs)
Date: Mon, 6 Apr 2020 14:21:33 -0400	[thread overview]
Message-ID: <20200406182133.GY1578@denix.org> (raw)
In-Reply-To: <alpine.LFD.2.21.2004061401020.22599@localhost.localdomain>

On Mon, Apr 06, 2020 at 02:01:45PM -0400, rpjday@crashcourse.ca wrote:
> On Mon, 6 Apr 2020, Richard Purdie wrote:
> 
> > On Mon, 2020-04-06 at 13:58 -0400, rpjday@crashcourse.ca wrote:
> > > On Mon, 6 Apr 2020, Quentin Schulz wrote:
> > >
> > > > On Mon, Apr 06, 2020 at 12:05:15PM -0400, rpjday@crashcourse.ca
> > > > wrote:
> > > > >   wanted to tweak the ref manual entry for PACKAGECONFIG, so a
> > > > > couple
> > > > > issues. first, the ref manual entry:
> > > > >
> > > > > https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PACKAGECONFIG
> > > > >
> > > > > says nothing about the possible *sixth* entry, described in
> > > > > base.bbclass as "foo_conflict_packageconfig", so i can add that
> > > > > but
> > > > > i'm open to proper wording since i'd probably screw it up.
> > > > > (i'd add an actual example from poky/ demonstrating this, such
> > > > > as:
> > > > >
> > > > > meta/recipes-support/curl/curl_7.69.1.bb:PACKAGECONFIG[threaded-
> > > > > resolver]
> > > > >   = "--enable-threaded-resolver,--disable-threaded-
> > > > > resolver,,,,ares"
> > > >
> > > > https://media.giphy.com/media/puPeyz4SOYEKY/giphy.gif
> > > > [minion screaming what]
> > > >
> > > > Didn't know about that one :) So PLEASE, document :)
> > >
> > >   yeah, that was one of those cases where i just wanted to match
> > > examples against the actual processing in base.bbclass, and went,
> > > "whoa, what the heck is *that*?" then went looking for examples. in
> > > fact, curl is a nice example, as it contains:
> > >
> > > # 'ares' and 'threaded-resolver' are mutually exclusive
> > > PACKAGECONFIG[ares] = "--enable-ares,--disable-ares,c-
> > > ares,,,threaded-resolver"
> > > ... snip ...
> > > PACKAGECONFIG[threaded-resolver] = "--enable-threaded-resolver,
> > > --disable-threaded-resolver,,,,ares"
> > >
> > > so that's the obvious example to demonstrate that. i'd never noticed
> > > that before.
> >
> > FWIW it was only added recently within the last month or so. We've not
> > got around to the docs for various reasons but happy to have help
> > there!
> 
>   ok, that explains it ... i'll put something together once i get to
> that point in the manual.

https://git.openembedded.org/openembedded-core/commit/?id=734475b3f86d88a548bc9eb91d836bd1b9335e9f

      reply	other threads:[~2020-04-06 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 16:05 couple questions on PACKAGECONFIG (for improving docs) rpjday
2020-04-06 16:38 ` [OE-core] " Quentin Schulz
2020-04-06 17:58   ` rpjday
2020-04-06 18:00     ` Richard Purdie
2020-04-06 18:01       ` rpjday
2020-04-06 18:21         ` Denys Dmytriyenko [this message]

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=20200406182133.GY1578@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quentin.schulz@streamunlimited.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=rpjday@crashcourse.ca \
    /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