Few years ago we replaced task-bootstrap with task-base to get better support for machine features. Today it generates lot of dependencies during build (mostly due to Bluetooth) and makes people think that their console images will contain X11.

There is a lot of information scattered across the OE, Bitbake, and Poky manuals, but the wiki doesn't have a lot of answers. It seems that that everything on the wiki is of limited scope - especially when it comes to troubleshooting build problems.

Whenever a new script is written by bitbake in temp/ (such as run.do_compile.11455), create or update a softlink (run.do_compile) that does not have the PID suffix.

Prevents you from finding the latest script during code development/debug cycles in the WORKDIR sources. Especially when you mix running the scripts with running bitbake this becomes hasslesome without a softlink.

Often one is testing a package and decides that the newer one is broken and chooses to write the recipe for an older version instead. do_clean doesnt remove the ipks/debs so re-bitbaking the package after cleaning up doesnt make a difference. do_rootfs will still pick up the newer versions' ipks, polluting the resulting image. This is especially painful when working with core packages like gtk/glib/dbus or anything that builds > 10-20 packages as one has to manually delete all these ipks. From experience, even leaving out one by mistake gave me ERRORs in do_rootfs logs and built half-complete images.

I believe that many of the complaints about openembedded, particularly those about it being "too general" or too difficult to coerce into generating teeny root filesystems are rooted in our image creation process.

Using recipes and packages for root filesystem creation is very limited. With a standalone powerful image building tool, you could give the user an interface to pick and choose individual files rather than our package based setup, or they could very easily tell it to take this or that external file and drop it into place, or install this package but without these certain files, etc.

If we can easily get a list of unmaintained packages, then new users can choose to volunteer to maintain a package as a way of starting their OpenEmbedded contributions.

These are created with the package and get installed in /var/lib/dpkg/info. Afterward it's a great way to find modified files for backup.

I vote for naming it "WITH", as it will control --with/--without in autotools projects.

This would allow people to write scripts to copy .debs/.ipks to another location and check them into configuration management.

Who's watching this film? Put your assessment (voits)!
Thank you!

I found this movie on this key
movie , download, online movie, watch , download , dvd, ipod, trailer, review