From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] utils/genrandconfig: add jquery-ui-themes handling
Date: Tue, 23 Aug 2022 11:30:51 +0200 [thread overview]
Message-ID: <20220823093051.GA2775145@scaer> (raw)
In-Reply-To: <20220821120304.GU2775145@scaer>
Fabrice, All,
On 2022-08-21 14:03 +0200, Yann E. MORIN spake thusly:
> On 2022-08-21 11:49 +0200, Yann E. MORIN spake thusly:
> > On 2022-08-20 13:33 +0200, Fabrice Fontaine spake thusly:
> > > Add a custom case to make sure that a random configuration with an empty
> > > theme for jquery-ui-themes doesn't fail. It reverts to
> > > BR2_PACKAGE_JQUERY_UI_THEMES_BLACK_TIE in that case.
> [--SNIP--]
> > I am not sure how we can end up with an empty BR2_PACKAGE_JQUERY_UI_THEMES_THEME.
> > Indeed, it is filled from a choice, and unless there is a typo in one of
> > the config options, there are as many defaults for it as there are
> > entries in the choice...
> >
> > And if you look at the .config file, there is actually something
> > selected in that choice, BR2_PACKAGE_JQUERY_UI_THEMES_VADER=y, but
> > indeed BR2_PACKAGE_JQUERY_UI_THEMES_THEME is not even set. It's not that
> > it is empty, it is not set at all!
> >
> > So, the .config file is not correct.
[--SNIP--]
> So, for fun, I had the following snippet run:
> while true; do
> ./utils/genrandconfig 2>&1 |grep KCONFIG_SEED=
> if grep -q BR2_PACKAGE_JQUERY_UI_THEMES=y .config; then
> echo 'Got JQuery UI themes...'
> grep BR2_PACKAGE_JQUERY_UI_THEMES_ .config
> grep -q BR2_PACKAGE_JQUERY_UI_THEMES_THEME= .config \
> || { echo 'Missing theme...'; break; }
> fi
> done
This has now been running for almost 48 hours straight, and there has
been 10005 configs generated, 55 with BR2_PACKAGE_JQUERY_UI_THEMES
enabled, of which none with BR2_PACKAGE_JQUERY_UI_THEMES_THEME unset.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-23 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 11:33 [Buildroot] [PATCH 1/1] utils/genrandconfig: add jquery-ui-themes handling Fabrice Fontaine
2022-08-21 9:49 ` Yann E. MORIN
2022-08-21 12:03 ` Yann E. MORIN
2022-08-23 9:30 ` Yann E. MORIN [this message]
2022-08-23 20:14 ` Arnout Vandecappelle
2022-08-24 9:32 ` Yann E. MORIN
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=20220823093051.GA2775145@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@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 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.