The current trend in OE recipes seems to use a wildcard in place of version numbers for bbappends. AFAIK this is a relatively new feature but a welcome one. This is a sort of RFC in that I think it's probably best for meta-selinux to use this mechanism to keep from having to rename bbappends everytime something in oe-core changes. I guess the right way to implement this is to change the bbappends in meta-selinux when the version numbers change upstream.
Philip Tricca (4): busybox: Use wildcard for version number in busybox bbappend. libcgroup: Use wildcard for version number in libcgroup bbappend. sudo: Use wildcard for version number in sudo bbappend. libxcb: Use wildcard for version number in libxcb bbappend. recipes-core/busybox/busybox_%.bbappend | 87 ++++++++++++++++++++++++ recipes-core/busybox/busybox_1.21.1.bbappend | 87 ------------------------ recipes-core/libcgroup/libcgroup_%.bbappend | 12 ++++ recipes-core/libcgroup/libcgroup_0.38.bbappend | 12 ---- recipes-extended/sudo/sudo_%.bbappend | 3 + recipes-extended/sudo/sudo_1.8.8.bbappend | 3 - recipes-graphics/xcb/libxcb_%.bbappend | 8 +++ recipes-graphics/xcb/libxcb_1.9.3.bbappend | 8 --- 8 files changed, 110 insertions(+), 110 deletions(-) create mode 100644 recipes-core/busybox/busybox_%.bbappend delete mode 100644 recipes-core/busybox/busybox_1.21.1.bbappend create mode 100644 recipes-core/libcgroup/libcgroup_%.bbappend delete mode 100644 recipes-core/libcgroup/libcgroup_0.38.bbappend create mode 100644 recipes-extended/sudo/sudo_%.bbappend delete mode 100644 recipes-extended/sudo/sudo_1.8.8.bbappend create mode 100644 recipes-graphics/xcb/libxcb_%.bbappend delete mode 100644 recipes-graphics/xcb/libxcb_1.9.3.bbappend -- 1.7.10.4 _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
