[OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill

[Laszlo Papp]

On Tue, Aug 13, 2013 at 11:35 AM, Jack Mitchell <ml at communistcode.co.uk>wrote:

> On 13/08/13 11:19, Laszlo Papp wrote:
> > I personally dislike top posting for a single entity in an email and I
> > think that is "nigh unbearable". ;-)
>
> If you also have a dislike for top-posting, then why top-post?!
>

That is a clear typo, as in: I personally dislike bottom posting for a
single entity.


> > More to the point, if there is no documentation, why is the bugreport
> > closed rather than forming it into a documentation bugreport?
>
> I am sure a bug-report for adding busybox config fragment documentation
> would be accepted.
>
>
> https://bugzilla.yoctoproject.org/buglist.cgi?product=General%20Docs&component=docs-general&resolution=---


No, I did mention documentation as well if there is a feature doing this,
but undocumented. That was apparently disregarded by the "team".


> > Also, I am still not sure we are on the same paper. You mean the python
> > script snippet will become optional? How will that mapping be done for
> > every possible options without adding explicit things to a feature set
> > like PACKAGECONFIG?
>
> I only answered the direct question in the email which is somewhere in
> the mess below, I couldn't bare to wade through the previous dredge.
> Hence, I have no idea with regards to any manual intervention with a
> python script. Going by the bug report, and the steps that I have seen,
> it should be automatic and as simple as dropping in a config fragment
> into the busybox recipe folder.
>

I have really no idea what you mean. You mean *every* defconfig entry is
mapped to a cfg, or what? This is still quite unclear to me how it is
supposed to work. Perhaps I should just wait for the "team" to realize this
in the bugreport, write documentation, and once that exists, I can
understand it. It is pretty hard to understand anything out of these
chunks, at least for me.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20130813/ac4a0103/attachment-0002.html>