From: Joshua Lock <joshua.lock@collabora.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/9] Fixes for a distro with a merged /usr
Date: Fri, 4 Sep 2015 15:59:37 +0100 [thread overview]
Message-ID: <cover.1441374016.git.joshua.lock@collabora.co.uk> (raw)
I've been playing around with building a distro with a merged /usr[1] and
the following series fixes several issues I ran across in OE core metadata.
These have been build tested by building a core-image-sato image with
ipk packaging for: i) qemux86 with a default configuration, ii) qemux86-64
with a mutlilib configuration where the image includes lib32-ncurses and
iii) for my merged /usr test distro.
I used buildhistory to compare core-image-sato before and after this series
and the only change is:
Changes to images/qemux86/glibc/core-image-sato (files-in-image.txt):
/bin/lsmod.kmod changed symlink target from ../bin/kmod to kmod
Changes since v1:
* Fix busybox typo/thinko which lead to installing busybox links into /usr/bin
* Fix systemd recipe to use nonarch_base_libdir for udev files
Regards,
Joshua
The following changes since commit aba3ef50d65e0dc8659a48bf98d0fb00dd44a6fc:
debianutils: create package for run-parts (2015-09-02 23:51:16 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib joshuagl/merged-usr
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=joshuagl/merged-usr
Joshua Lock (9):
kmod: fix link creation when base_bindir != /bin
busybox: fixes for when base_bindir != /bin
systemd: remove hard-coded paths in FILES entries
alsa-utils: handle udev dir being 2 levels below /
pulseaudio: handle udev dir being 2 levels below /
bluez: handle udev dir being 2 levels below /
pcmciautils: handle udev dir being 2 levels below /
nfs-utils: don't force use of /sbin as sbindir
procps: fix for base_sbindir == sbindir
meta/recipes-bsp/pcmciautils/pcmciautils_018.bb | 4 +-
meta/recipes-connectivity/bluez5/bluez5.inc | 1 +
.../nfs-utils/nfs-utils_1.3.1.bb | 8 ++++
meta/recipes-core/busybox/busybox.inc | 49 ++++++++++++----------
meta/recipes-core/systemd/systemd_219.bb | 10 ++---
meta/recipes-extended/procps/procps_3.3.10.bb | 5 ++-
meta/recipes-kernel/kmod/kmod_git.bb | 4 +-
meta/recipes-multimedia/alsa/alsa-utils_1.0.29.bb | 2 +-
meta/recipes-multimedia/pulseaudio/pulseaudio.inc | 2 +-
9 files changed, 49 insertions(+), 36 deletions(-)
--
2.1.4
next reply other threads:[~2015-09-04 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 14:59 Joshua Lock [this message]
2015-09-04 14:59 ` [PATCH v2 1/9] kmod: fix link creation when base_bindir != /bin Joshua Lock
2015-09-04 22:11 ` Richard Purdie
2015-09-04 14:59 ` [PATCH v2 2/9] busybox: fixes for " Joshua Lock
2015-09-04 14:59 ` [PATCH v2 3/9] systemd: remove hard-coded paths in FILES entries Joshua Lock
2015-09-04 14:59 ` [PATCH v2 4/9] alsa-utils: handle udev dir being 2 levels below / Joshua Lock
2015-09-04 14:59 ` [PATCH v2 5/9] pulseaudio: " Joshua Lock
2015-09-04 14:59 ` [PATCH v2 6/9] bluez: " Joshua Lock
2015-09-04 14:59 ` [PATCH v2 7/9] pcmciautils: " Joshua Lock
2015-09-04 14:59 ` [PATCH v2 8/9] nfs-utils: don't force use of /sbin as sbindir Joshua Lock
2015-09-04 14:59 ` [PATCH v2 9/9] procps: fix for base_sbindir == sbindir Joshua Lock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1441374016.git.joshua.lock@collabora.co.uk \
--to=joshua.lock@collabora.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox