> From: Paul Eggleton
>
> There are a few useful tools here. Firstly, "bitbake-layers
> show-recipes" will
> list all recipes available in your current configuration, the
> versions
> available and which layers they are provided by. You can also
> specify a search keyword on the command line.
>
> Additionally, "bitbake -s" will list all available "targets"
> (recipes, plus
> any BBCLASSEXTENDed variants, e.g. zlib-native) and the
> latest and current preferred versions.
>
> Lastly, if you want to search all available recipes in
> community layers, there
> is now an online metadata index available:
>
> http://layers.openembedded.org/
I found the first one, and the second seems to show mostly the same info in
a different form.
What I don't see is any info on the recipes, beyond name and version number.
I don't see a list of packages they produce. For instance, doing "bitbake -e
samba", and then looking at the PACKAGES variable, shows the following list:
libwbclient
libwinbind
libwinbind-dbg
winbind
winbind-dbg
libnetapi
libtdb
libsmbsharemodes
libsmbclient
libsmbclient-dev
cifs
cifs-doc
swat
samba-dbg
samba-staticdev
samba-dev
samba-doc
samba-locale
samba
I'm not sure what got included when I added "samba" to my IMAGE_INSTALL
variable, but I assume samba and winbind are required, but the other things?
To an end user like me (someone who just wants to build a distro with
certain capabilities, and then get back to the real work of application
development), the following sorts of questions occur:
What choices are provided by each package?
If something is included in the build, can I do without it?
If something isn't included in the build, should I add it?
To be a real turn-key system, each recipe needs a page, or two, or three, of
human-written (not script-produced) explanation of what options the recipe
has, what they correspond to in user terms, and how they can be selected or
deselected. Without that, the recipe really isn't "documented" in the
conventional sense.
When I added samba to core-image-base-cedartrail-nopvr, the image got vastly
bigger. I wouldn't think the ability to do Windows file sharing would be
comparable in size to the rest of the system. Did it add tons of man pages
which no one will read, because it's an embedded system? Did it add a client
which I don't need, or just the server which I do need? Did it add libraries
to the target that will never be used? Eventually, I'll figure this out, but
I'm spending weeks and weeks on this, which is making this a very expensive
project. Perhaps I should have just hired someone else to do it for me.
--
Ciao, Paul D. DeRocco
Paul mailto:pdero...@ix.netcom.com
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
