The status of recipes are marked red to flag that they
need further upgrading.
- libusb-compat was classified as base utils, put it to base libs
- rpm was not in poky-image-{sato,sdk}, but since we are in transition
to rpm based packaging, include it as well
- libsoup should be handled together with libsoup-2.4
- tinylogin has been merged into busybox
33 recipes to go
Signed-off-by: Qing He <qing.he@intel.com>
another fix is to remove ${docdir} appending to FILES_${PN}-doc,
since it's already included by FILES_${PN}-doc
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
(borrow from OE 2.24.0, with study about reason for detail changes)
[Patches-Poky]
KEEP _configure-libtool.patch_: fix cross-build env
REMOVE _glibconfig-sysdefs.h_: introduced in glib-1.2.10, which is actually
not valid today
KEEP _glib-gettexize-dir.patch_: another quite old patch added before 2.10.3
add history info, and mark for upstream
[Patches-OE]
NOTAKE _gio.patch_: a private extension for a window matching library (wncksync)
NOTAKE _gvavriant.patch_: in 2.24.1 now
NOTAKE _gasync.patch_: in 2.24.1 now
TAKE _60_wait-longer-for-threads-to-die.patch: said to fix anonying warning
TAKE _gatomic-proper-get-cast.patch_: fix error about type casting. Instead of
using OE's patch, I found a better one from latest repo
NOTAKE _g_once_init_enter.patch_: in OE since 2.22.1, not quite sure of its purpose,
also it's not in upstream yet
[Recipe]
- fix metadata
- keep glib-2.inc which is for python optimization
- remove PRIORITY since 'optional' is the default
- no need to specially install glibconfig.h in ad hoc path, which is only relied
by 'obexpush' which poky doesn't have and can be fixed in 'obexpush' itself as
what OE does
- no need to manually create glib2.0/glib, which is handled by current code
- remove 'acpaths' which only applies to versions before 2.12.4
- below lines are not taken from OE
* glib-mkenums tweaks, which exists in OE for a long time but never in poky.
since there's no way to find out original commit, keep poky's style instead.
* host libtool check. not sure about its purpose, and it's also in OE for quite
long time
Signed-off-by Kevin Tian <kevin.tian@intel.com>
Old 1.6.8p12 is quite old, even w/o source available now (only cached in pokylinux).
[Patches-Poky]
KEEP _autofoo.patch_: deal with bunch of autotool warnings/errors, more about
underquotes. In 1.7.2p7, those error conditions disappear.
But the underquotes fix is still valid to remove a bunch
of autoconf warnings
REMOVE _autofoo1.patch_: copy of autofoo.patch. no one uses it. REMOVE.
KEEP _noexec-link.patch_: use "-module" to avoid libtool complaining about not
starting with "lib". Add comment to the patch file.
DISABLE _nostrip.patch_: it's wrong to strip target binaries on build host. Borrow
from OE to use 'sed' instead of patch, but keept it for
remind to upstream
REMOVE _nonrootinstall.patch_: handle mode/owner population at install. It's not
requried at all since there's pkg_postinst to handle
it at right stage
Other misc stuff:
- update metadata information
- no need to use ${S} in 1.7.2p7
- fix idention
- use sed to disable strip
- changes from OE:
* disable PAM as our pam doesn't include necessary config files and plugs
* no need to special sudo_cv_uid_t_len tweak in the recipe. It's already there
in poky site files for a long time
* move sudo_cv_func_unsetenv_void to meta/site/common. Stdlib.h is common across
architectures in our libc headers, which conforms to POSIX standard
(borrow from openembedded 1.7.2p4)
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Likely cause is, of course, typo in the pattern or incorrect BBFILES, so we
should warn the user about this.
(Bitbake rev: b781317b5006bc047a59e7fa3c93344115e78ccb)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
This failure is one the *user* needs to see, as it may have to do with their
setup, but where they don't need to see a traceback and all, since they're not
developers, so I think SystemExit is appropriate here.
(Bitbake rev: e3cc9bc7b6ef1a2eca78235790a051329bceb9a4)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
causes exceptions to not be handled after the finally statement
(Bitbake rev: 1a04610dea376340b9ea4c109f64995b4fd6ad02)
Signed-off-by: Cliff Brake <cbrake@bec-systems.com>
Signed-off-by: Chris Larson <clarson@kergoth.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
This is necessary, as there has not yet been a release with the bb.utils
versions in place. We can't show them a deprecation warning when they can't
safely change it yet. Show a PendingDeprecationWarning until 1.10 releases
and OE requires it, then we can move to DeprecationWarning.
(Bitbake rev: 43700fa1ca1d2635de4ed46110057cb164ee82d1)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Fixes proxy support to honor standard proxy environment variables.
* Quote environment variables
(Bitbake rev: f84f382f340d6db15b9e5afb8c7c93969249a958)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Qing He
Kevin Tian
Richard Purdie
Chris Larson
Cliff Brake
Ryan Phillips
Bernhard Reutner-Fischer