is the ref manual DISTRO_FEATURES list meant to be exhaustive?

is the ref manual DISTRO_FEATURES list meant to be exhaustive?

[Robert P. J. Day]

  just noticed that the list of DISTRO_FEATURES values listed here:

http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-features-distro

is somewhat incomplete. is that deliberate? just from poking around
the dora release, i can see tests for DISTRO_FEATURES values of ptest,
directfb, pam, zeroconf, acl, xattr, sysvinit and more. should those
values also be part of that list, or is the ref manual only attempting
to present a subset?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: is the ref manual DISTRO_FEATURES list meant to be exhaustive?

[Paul Eggleton]

Hi Robert,

On Thursday 14 November 2013 09:05:09 Robert P. J. Day wrote:
>   just noticed that the list of DISTRO_FEATURES values listed here:
> 
> http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-featu
> res-distro
> 
> is somewhat incomplete. is that deliberate? just from poking around
> the dora release, i can see tests for DISTRO_FEATURES values of ptest,
> directfb, pam, zeroconf, acl, xattr, sysvinit and more. should those
> values also be part of that list, or is the ref manual only attempting
> to present a subset?

It's meant to be complete. I think as new values have been introduced we have 
neglected to add them to the list, but they should be added.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: is the ref manual DISTRO_FEATURES list meant to be exhaustive?

[Robert P. J. Day]

On Thu, 14 Nov 2013, Paul Eggleton wrote:

> Hi Robert,
>
> On Thursday 14 November 2013 09:05:09 Robert P. J. Day wrote:
> >   just noticed that the list of DISTRO_FEATURES values listed here:
> >
> > http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-featu
> > res-distro
> >
> > is somewhat incomplete. is that deliberate? just from poking around
> > the dora release, i can see tests for DISTRO_FEATURES values of ptest,
> > directfb, pam, zeroconf, acl, xattr, sysvinit and more. should those
> > values also be part of that list, or is the ref manual only attempting
> > to present a subset?
>
> It's meant to be complete. I think as new values have been introduced we have
> neglected to add them to the list, but they should be added.

  i can open a bugzilla issue for this, what category (General Docs?)
and subcatgory should i use?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: is the ref manual DISTRO_FEATURES list meant to be exhaustive?

[Robert P. J. Day]

On Thu, 14 Nov 2013, Paul Eggleton wrote:

> Hi Robert,
>
> On Thursday 14 November 2013 09:05:09 Robert P. J. Day wrote:
> >   just noticed that the list of DISTRO_FEATURES values listed here:
> >
> > http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-featu
> > res-distro
> >
> > is somewhat incomplete. is that deliberate? just from poking
> > around the dora release, i can see tests for DISTRO_FEATURES
> > values of ptest, directfb, pam, zeroconf, acl, xattr, sysvinit and
> > more. should those values also be part of that list, or is the ref
> > manual only attempting to present a subset?
>
> It's meant to be complete. I think as new values have been
> introduced we have neglected to add them to the list, but they
> should be added.

  in case this is helpful, here's the full list i came up with using a
simple grep search looking through the dora 10.0 source tree for
DISTRO_FEATURES tests of values that aren't listed in section 10.1 of
the ref manual:

 3g
 acl
 directfb
 ipv4
 largefile
 libc-posix-clang-wchar
 ld-is-gold
 multiarch
 nfc
 openvg
 pam
 pie
 pulseaudio
 ptest
 sysvinit
 x11
 xattr
 zeroconf

conversely, there *are* a few values listed in section 10.1 of the ref
manual that don't appear to be tested for anywhere (typo? obsolete?)

 ext2
 irda (this is a MACHINE feature but not a DISTRO feature)
 sdk-pms

for what it's worth. i'm about to do the same scan for
MACHINE_FEATURES.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: is the ref manual DISTRO_FEATURES list meant to be exhaustive?

[David Nyström]

Hi,

I sent the sdk-pms patch/es, it seems to have been merged to poky-docs but not in oe-core.
Richard, how do you want this fixed ?

//DD


Sent from my Android phone using TouchDown (www.nitrodesk.com)


-----Original Message-----
From: Robert P. J. Day [rpjday@crashcourse.ca]
Received: Friday, 15 Nov 2013, 11:29
To: Paul Eggleton [paul.eggleton@linux.intel.com]
CC: yocto@yoctoproject.org [yocto@yoctoproject.org]
Subject: Re: [yocto] is the ref manual DISTRO_FEATURES list meant to be exhaustive?


On Thu, 14 Nov 2013, Paul Eggleton wrote:

> Hi Robert,
>
> On Thursday 14 November 2013 09:05:09 Robert P. J. Day wrote:
> >   just noticed that the list of DISTRO_FEATURES values listed here:
> >
> > http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-featu
> > res-distro
> >
> > is somewhat incomplete. is that deliberate? just from poking
> > around the dora release, i can see tests for DISTRO_FEATURES
> > values of ptest, directfb, pam, zeroconf, acl, xattr, sysvinit and
> > more. should those values also be part of that list, or is the ref
> > manual only attempting to present a subset?
>
> It's meant to be complete. I think as new values have been
> introduced we have neglected to add them to the list, but they
> should be added.

  in case this is helpful, here's the full list i came up with using a
simple grep search looking through the dora 10.0 source tree for
DISTRO_FEATURES tests of values that aren't listed in section 10.1 of
the ref manual:

 3g
 acl
 directfb
 ipv4
 largefile
 libc-posix-clang-wchar
 ld-is-gold
 multiarch
 nfc
 openvg
 pam
 pie
 pulseaudio
 ptest
 sysvinit
 x11
 xattr
 zeroconf

conversely, there *are* a few values listed in section 10.1 of the ref
manual that don't appear to be tested for anywhere (typo? obsolete?)

 ext2
 irda (this is a MACHINE feature but not a DISTRO feature)
 sdk-pms

for what it's worth. i'm about to do the same scan for
MACHINE_FEATURES.

rday

--

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: is the ref manual DISTRO_FEATURES list meant to be exhaustive?

[Robert P. J. Day]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 706 bytes --]

On Fri, 15 Nov 2013, David Nyström wrote:

> Hi,
>
> I sent the sdk-pms patch/es, it seems to have been merged to
> poky-docs but not in oe-core. Richard, how do you want this fixed ?

  whoops, guess we can ignore that patch of mine from 60 seconds ago,
then.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: is the ref manual DISTRO_FEATURES list meant to be exhaustive?

[Robert P. J. Day]

  a list of apparent necessary updates to section 10 of the ref
manual, lists of valid items for DISTRO_FEATURES and MACHINE_FEATURES:

http://www.crashcourse.ca/wiki/index.php/OE#_FEATURES_updates_for_Section_10_of_reference_manual

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: is the ref manual DISTRO_FEATURES list meant to be exhaustive?

[Paul Eggleton]

Hi Robert,

On Friday 15 November 2013 14:43:30 Robert P. J. Day wrote:
>   a list of apparent necessary updates to section 10 of the ref
> manual, lists of valid items for DISTRO_FEATURES and MACHINE_FEATURES:
> 
> http://www.crashcourse.ca/wiki/index.php/OE#_FEATURES_updates_for_Section_10
> _of_reference_manual

You're right that there are some missing from the list; I agree that we should 
document all of the ones we support in OE-Core. However, I don't think we want 
to include the libc-* ones (at least, not listing all of them; providing a 
pointer to how you can get the list for eglibc might be useful though, 
possibly with reference to how these features normally get into 
DISTRO_FEATURES i.e. via DISTRO_FEATURES_LIBC_DEFAULT -> DISTRO_FEATURES_LIBC 
).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre