Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCHv2 6/6] README.LSB: describe oe-core's deviations from the LSB spec
Date: Fri,  5 May 2017 17:10:27 +0300	[thread overview]
Message-ID: <20170505141027.8381-6-alexander.kanavin@linux.intel.com> (raw)
In-Reply-To: <20170505141027.8381-1-alexander.kanavin@linux.intel.com>

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 README.LSB | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 README.LSB

diff --git a/README.LSB b/README.LSB
new file mode 100644
index 00000000000..c9dca3fc75e
--- /dev/null
+++ b/README.LSB
@@ -0,0 +1,25 @@
+OE-Core aims to be able to provide basic LSB compatible images. There
+are some challenges for OE as LSB isn't always 100% relevant to its
+target embedded and IoT audiences. 
+
+One challenge is that the LSB spec is no longer being actively
+developed [https://github.com/LinuxStandardBase/lsb] and has 
+components which are end of life or significantly dated. OE 
+therefore provides compatibility with the following caveats:
+
+* Qt4 is provided by the separate meta-qt4 layer. Its noted that Qt4 
+  is end of life and this isn't something the core project regularly 
+  tests any longer. Users are recommended to group together to support
+  maintenance of that layer. [http://git.yoctoproject.org/cgit/cgit.cgi/meta-qt4/]
+
+* mailx has been dropped since its no longer being developed upstream 
+  and there are better, more modern replacements such as s-nail 
+  (http://sdaoden.eu/code.html) or mailutils (http://mailutils.org/).
+
+* A few perl modules that were required by LSB 4.x aren't provided:
+  libclass-isa, libenv, libdumpvalue, libfile-checktree,
+  libi18n-collate, libpod-plainer.
+
+* libpng 1.2 isn't provided; oe-core includes the latest release of libpng
+  instead.
+
-- 
2.11.0



      parent reply	other threads:[~2017-05-05 14:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 14:10 [PATCHv2 1/6] liberation-fonts: update to 2.00.1 Alexander Kanavin
2017-05-05 14:10 ` [PATCHv2 2/6] packagegroup-core-lsb: do not include Qt4 anymore Alexander Kanavin
2017-05-05 14:10 ` [PATCHv2 3/6] libpng12: remove the recipe Alexander Kanavin
2017-05-05 14:10 ` [PATCHv2 4/6] recipes-lsb4/perl: remove the recipes Alexander Kanavin
2017-05-05 14:13   ` Tim Orling
2017-05-05 14:15     ` Alexander Kanavin
2017-05-05 14:10 ` [PATCHv2 5/6] mailx: remove the recipe Alexander Kanavin
2017-05-05 14:10 ` Alexander Kanavin [this message]

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=20170505141027.8381-6-alexander.kanavin@linux.intel.com \
    --to=alexander.kanavin@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