All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: preferred KERNEL_FEATURES format: netfilter or netfilter.scc?
Date: Tue, 3 Mar 2015 11:30:12 -0500	[thread overview]
Message-ID: <54F5E194.5010404@windriver.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1503031124590.15385@Device-040570>

On 15-03-03 11:27 AM, Robert P. J. Day wrote:
> On Tue, 3 Mar 2015, Bruce Ashfield wrote:
>
>> On 15-03-03 05:39 AM, Robert P. J. Day wrote:
>>> On Tue, 3 Mar 2015, Robert P. J. Day wrote:
>>>
>>>>
>>>>     kernel dev manual uses the KERNEL_FEATURES format of:
>>>>
>>>>        KERNEL_FEATURES += "features/netfilter.scc"
>>>>
>>>> while ref manual variable glossary uses
>>>>
>>>>        KERNEL_FEATURES="features/netfilter"
>>>>
>>>> is there a preference for the usage of the .scc suffix? (i'm assuming
>>>> they're both valid, i didn't actually check that. maybe i should check
>>>> that ...)
>>>
>>>     hang on, i think there's an error in the docs ... if i check the
>>> meta branch, i see that the actual structure for the netfilter feature
>>> is "features/netfilter/netfilter.scc", so "features/netfilter.scc"
>>> shouldn't even work, should it? historical remnant?
>>
>> It works, but it is an old shortcut that isn't emphasized or used.
>> So yes, its a historical remnant, and explicit .scc references are
>> preferred.
>
>    wait ... just to be clear, you're saying that referring to a
> features *directory* is a historical remnant? note above that i'm
> asking about what appears to be a historical remnant where it looks
> like netfilter used to be a .scc file directly under features/, now
> it's in a subdirectory.

This format:  KERNEL_FEATURES="features/netfilter"

Is the historical remnant. The tools can convert that to
features/netfilter/netfiler.scc internally. It was a shortcut to
make the features more human readable when they followed that
defined form "<dirname>/<dirname>.scc"

>
>    as it stands now, it would *appear* that the statement:
>
>    KERNEL_FEATURES += "features/netfilter.scc"
>
> is simply wrong and can't possibly work, correct?

That one is wrong, but the tools can also do a basename before
running the test, which converts it to that other format, and
then it can be expanded to find the feature description.

Both are non-obvious, and error prone .. hence why they are not
used anymore.

So the answer is that the docs should be updated to purge the
old references.

Bruce

>
> rday
>



  reply	other threads:[~2015-03-03 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  9:12 preferred KERNEL_FEATURES format: netfilter or netfilter.scc? Robert P. J. Day
2015-03-03 10:39 ` Robert P. J. Day
2015-03-03 14:29   ` Bruce Ashfield
2015-03-03 16:27     ` Robert P. J. Day
2015-03-03 16:30       ` Bruce Ashfield [this message]
2015-03-03 16:46         ` Robert P. J. Day

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=54F5E194.5010404@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=rpjday@crashcourse.ca \
    --cc=yocto@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.