From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Mihai Lindner <mihaix.lindner@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] lsb_release: add sanity to avoid Unknown
Date: Fri, 26 Oct 2012 15:44:44 +0100 [thread overview]
Message-ID: <3432214.SFZEzFPHYM@helios> (raw)
In-Reply-To: <040de77b972b11336e88c593cf2a7571977347db.1351261721.git.mihaix.lindner@linux.intel.com>
On Friday 26 October 2012 17:37:17 Mihai Lindner wrote:
> Check for lsb_release command (package name should be lsb-release for
> most package managers) to avoid "Unknown" Linux distributions, untested
> distro warnings and "Unknown" dir in ./sstate-cache/
> Also add lsb-release in host's software needs, Fedora and CentOS for now.
>
> Signed-off-by: Mihai Lindner <mihaix.lindner@linux.intel.com>
> ---
> documentation/poky.ent | 4 ++--
> meta/classes/sanity.bbclass | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/documentation/poky.ent b/documentation/poky.ent
> index 8e0af71..ae8e70e 100644
> --- a/documentation/poky.ent
> +++ b/documentation/poky.ent
> @@ -50,8 +50,8 @@
> <!ENTITY OE_INIT_FILE "oe-init-build-env">
> <!ENTITY UBUNTU_HOST_PACKAGES_ESSENTIAL "awk wget git-core diffstat unzip
> texinfo build-essential chrpath"> <!ENTITY FEDORA_HOST_PACKAGES_ESSENTIAL
> "awk make wget tar bzip2 gzip python unzip perl patch diffutils diffstat
> git -cpp gcc gcc-c++ eglibc-devel texinfo chrpath ccache">
> +cpp gcc gcc-c++ eglibc-devel texinfo chrpath ccache lsb-release">
> <!ENTITY OPENSUSE_HOST_PACKAGES_ESSENTIAL "python gcc gcc-c++ git chrpath
> make wget diffstat texinfo python-curses"> <!ENTITY
> CENTOS_HOST_PACKAGES_ESSENTIAL "gawk make wget tar bzip2 gzip python unzip
> perl patch diffutils diffstat git -cpp gcc gcc-c++ glibc-devel texinfo
> chrpath">
> +cpp gcc gcc-c++ glibc-devel texinfo chrpath lsb-release">
>
> diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
> index 3806bc5..f0cc11c 100644
> --- a/meta/classes/sanity.bbclass
> +++ b/meta/classes/sanity.bbclass
> @@ -2,7 +2,7 @@
> # Sanity check the users setup for common misconfigurations
> #
>
> -SANITY_REQUIRED_UTILITIES ?= "patch diffstat makeinfo git bzip2 tar gzip
> gawk chrpath wget cpio" +SANITY_REQUIRED_UTILITIES ?= "bzip2 chrpath cpio
> diffstat gawk git gzip lsb_release makeinfo patch tar wget"
>
> python check_bblayers_conf() {
> bblayers_fn = os.path.join(d.getVar('TOPDIR', True),
> 'conf/bblayers.conf')
I don't particularly like this, because on some distros LSB comes as one
package which pulls in a whole bunch of unnecessary things for a headless
server. I think we need an alternative fix for this for the cases where
lsb_release is not available.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-10-26 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 14:37 [PATCH 0/2] check lsb_release exists and avoid sstate subdirectory Mihai Lindner
2012-10-26 14:37 ` [PATCH 1/2] lsb_release: add sanity to avoid Unknown Mihai Lindner
2012-10-26 14:44 ` Paul Eggleton [this message]
2012-10-26 15:25 ` Mihai Lindner
2012-10-26 15:43 ` Mihai Lindner
2012-10-26 14:37 ` [PATCH 2/2] distro_identifier: replace slash with hyphen Mihai Lindner
2012-10-28 1:20 ` Saul Wold
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=3432214.SFZEzFPHYM@helios \
--to=paul.eggleton@linux.intel.com \
--cc=mihaix.lindner@linux.intel.com \
--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