From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Damian, Alexandru" <alexandru.damian@intel.com>
Cc: "webhob@yoctoproject.org" <webhob@yoctoproject.org>
Subject: Re: [Webhob] updating documentation.conf
Date: Thu, 22 Aug 2013 16:26:15 +0100 [thread overview]
Message-ID: <1397947.SpZsfi66oa@helios> (raw)
In-Reply-To: <CAJ2CSBsq3_ZqxsHwFtfLk=VtVW_azFHCFD2Mw=pR3WCa8+_OQQ@mail.gmail.com>
On Thursday 22 August 2013 16:02:05 Damian, Alexandru wrote:
> On Wed, Aug 21, 2013 at 4:51 PM, Barros Pena, Belen <
> belen.barros.pena@intel.com> wrote:
> > The information I added to documentation.conf is now showing up in Web Hob
> > (thanks, Alex!).
> >
> > Looking at it, it seems that the description is not picked up for
> > variables with a suffix (things like PREFERRED_PROVIDER_xyz). Could that
> > be fixed? Do you want an issue in Bugzilla for this?
>
> not sure how this should be handled, Paul thinks it should be in there ?
>
> AFAIK, suffixed variables get used instead of the normal ones, so they are
> more like replacements.
> I guess the design ask that we should the only the variables with doc
> attached, so they would be hidden.
>
> Isn't this the case ?
I think that variables like PREFERRED_PROVIDER are kind of a special case -
their overrides will never be in OVERRIDES except when bitbake is reading from
them. If we want to show them in the variables list then we might have to
handle them specially (or just do something like cut the variable name back to
the last capital letter in order to look up the doc flag).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-08-22 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 10:40 [Webhob] updating documentation.conf Barros Pena, Belen
2013-08-16 10:24 ` Richard Purdie
2013-08-21 15:51 ` Barros Pena, Belen
2013-08-22 15:02 ` Damian, Alexandru
2013-08-22 15:26 ` Paul Eggleton [this message]
2013-08-22 15:40 ` Barros Pena, Belen
2013-08-22 17:11 ` Richard Purdie
2013-08-22 17:32 ` Barros Pena, Belen
2013-08-22 20:53 ` Damian, Alexandru
2013-08-22 22:26 ` Richard Purdie
2013-08-23 8:54 ` Barros Pena, Belen
2013-08-23 14:02 ` Damian, Alexandru
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=1397947.SpZsfi66oa@helios \
--to=paul.eggleton@linux.intel.com \
--cc=alexandru.damian@intel.com \
--cc=webhob@yoctoproject.org \
/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.