[oe] [meta-oe] [PATCH] libedit: upgrade 20181209-3.1 -> 20190324-3.1
-Upgrade from libedit_20181209-3.1.bb to libedit_20190324-3.1.bb.
Signed-off-by: Zang Ruochen
---
.../{libedit_20181209-3.1.bb => libedit_20190324-3.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-oe/recipes-devtools/libedit/{libedit_20181209-3.1.bb =>
libedit_20190324-3.1.bb} (81%)
diff --git a/meta-oe/recipes-devtools/libedit/libedit_20181209-3.1.bb
b/meta-oe/recipes-devtools/libedit/libedit_20190324-3.1.bb
similarity index 81%
rename from meta-oe/recipes-devtools/libedit/libedit_20181209-3.1.bb
rename to meta-oe/recipes-devtools/libedit/libedit_20190324-3.1.bb
index c0a3d2136..9d333e7aa 100644
--- a/meta-oe/recipes-devtools/libedit/libedit_20181209-3.1.bb
+++ b/meta-oe/recipes-devtools/libedit/libedit_20190324-3.1.bb
@@ -15,8 +15,8 @@ FETCHCMD_wget += "-U bitbake"
SRC_URI = "http://www.thrysoee.dk/editline/${BPN}-${PV}.tar.gz \
file://stdc-predef.patch \
"
-SRC_URI[md5sum] = "22e945a0476e388e6f78bfc8d6e1192c"
-SRC_URI[sha256sum] =
"2811d70c0b000f2ca91b7cb1a37203134441743c4fcc9c37b0b687f328611064"
+SRC_URI[md5sum] = "bec755c8044ad84b752dfe49a0b371d8"
+SRC_URI[sha256sum] =
"ac8f0f51c1cf65492e4d1e3ed2be360bda41e54633444666422fbf393bba1bae"
S = "${WORKDIR}/${BPN}-${PV}"
--
2.20.1
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe] [PATCH] augeas: upgrade 1.10.1 -> 1.11.0
-Upgrade from augeas_1.10.1.bb to augeas_1.11.0.bb. Signed-off-by: Zang Ruochen --- meta-oe/recipes-support/augeas/augeas_1.10.1.bb | 4 meta-oe/recipes-support/augeas/augeas_1.11.0.bb | 4 2 files changed, 4 insertions(+), 4 deletions(-) delete mode 100644 meta-oe/recipes-support/augeas/augeas_1.10.1.bb create mode 100644 meta-oe/recipes-support/augeas/augeas_1.11.0.bb diff --git a/meta-oe/recipes-support/augeas/augeas_1.10.1.bb b/meta-oe/recipes-support/augeas/augeas_1.10.1.bb deleted file mode 100644 index 26e191bd3..0 --- a/meta-oe/recipes-support/augeas/augeas_1.10.1.bb +++ /dev/null @@ -1,4 +0,0 @@ -require augeas.inc - -SRC_URI[md5sum] = "6c0b2ea6eec45e8bc374b283aedf27ce" -SRC_URI[sha256sum] = "52db256afab261d31cc147eaa1a71795a5fec59e888dfd0b65a84c7aacd6364d" diff --git a/meta-oe/recipes-support/augeas/augeas_1.11.0.bb b/meta-oe/recipes-support/augeas/augeas_1.11.0.bb new file mode 100644 index 0..cdd11beec --- /dev/null +++ b/meta-oe/recipes-support/augeas/augeas_1.11.0.bb @@ -0,0 +1,4 @@ +require augeas.inc + +SRC_URI[md5sum] = "abf51f4c0cf3901d167f23687f60434a" +SRC_URI[sha256sum] = "393ce8f4055af89cd4c20bf903eacbbd909cf427891f41b56dc2ba66243ea0b0" -- 2.20.1 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] [OE-core] Git commit process question.
On Wed, Apr 3, 2019 at 4:07 PM Paul Eggleton wrote: > > On Thursday, 4 April 2019 5:46:04 AM NZDT Khem Raj wrote: > > On Wed, Apr 3, 2019 at 7:41 AM Tom Rini wrote: > > > > > > On Wed, Apr 03, 2019 at 11:30:39AM +0100, Burton, Ross wrote: > > > > On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote: > > > > > > The kernel does not have "upgrade foo to the latest upstream > > > > > > version" commits. > > > > > > > > > > > > With the Automatic Upgrade Helper this is a semi-automatic task, and > > > > > > most of the time there is no specific motivation other than > > > > > > upgrading > > > > > > to the latest upstream version. > > > > > > > > > > But since that's just filling in a template the body can also be a > > > > > template perhaps with useful AUH data (run at ... by ... ?) ? > > > > > > > > Apart from making the commit message longer what does this achieve? > > > > The commit already has a timestamp and author. > > > > > > It's an etiquette thing. Subject+Sign-off+Empty body is bad form. AUH > > > updates are a form of "trivial update" that every project has. "Update > > > $X from version $Y to $Z" is what a human would normally put. It's > > > weird looking at git log of nothing but subject+signed-off-by. I'm not > > > going to object further on this point, but I don't get it. > > > > if the content of subject is being repeated in body then I would > > prefer an empty body > > redundant information in commits should be avoided since it can create > > impression that body does not have > > useful information and skip reading it. We should strive to make commits > > concise and useful. > > There is often (I won't say always, but often) something useful you can put in > the commit message. If it's a recipe upgrade, you could put a pointer to the > upstream changelog in it, for example. As the person doing the upgrade if your > prior review of that changelog or other upstream release documentation > indicated any backwards-compatibility issues or CVEs fixed then those really > ought to be mentioned as well; if you're feeling especially generous you might > mention highlights of any new functionality. (I have a proposal that might > help us automate part of that which I've not yet fully fleshed out, hopefully > one day soon I will get around to it.) > > The issue of empty commit messages is something I've complained about in the > past, and not just about recipe upgrades. If I - as someone who is relatively > familiar with OE - have to actually read beyond the shortlog / commit message > to understand the basics of why a change has been made, then it's likely that > the commit message wasn't good enough. Unlike other issues, once a commit goes > in the message is set in stone within the git history, so if you are working > on a change, *please* take a minute or two to document it adequately in the > commit message so that others looking back can understand it. > Definitely, and I agree that we should put relevant information in commits, usually the information about side effects if any, links to changelog etc. are useful too however, we should not enforce a behavior which could result in redundancy as explained > Thanks, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre > > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [PATCH 2/2] gnome-desktop3: rework gobject-introspection handling
gobject-introspection is mandatory for gnome-desktop3 - there is no configure option to enable or disable it. To handle properly, this patch does: * Make 'gobject-introspection-data' a required distro feature * To avoid trouble once pending patch removing 'UNKNOWN_CONFIGURE_WHITELIST_append = " --enable-introspection --disable-introspection"' are in oe-core [1] - set in recipe to avoid | ERROR: gnome-desktop3-3.32.0-r0 do_configure: QA Issue: gnome-desktop3: configure was passed unrecognised options: introspection [unknown-configure-option] This does not handle MACHINE_FEATURES / qemu-usermode case but there other issues of higher priority. [1] http://lists.openembedded.org/pipermail/openembedded-core/2019-April/280711.html Signed-off-by: Andreas Müller --- .../recipes-gnome/gnome-desktop/gnome-desktop3_3.32.0.bb| 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/meta-gnome/recipes-gnome/gnome-desktop/gnome-desktop3_3.32.0.bb b/meta-gnome/recipes-gnome/gnome-desktop/gnome-desktop3_3.32.0.bb index c1a67bda9..bba81663d 100644 --- a/meta-gnome/recipes-gnome/gnome-desktop/gnome-desktop3_3.32.0.bb +++ b/meta-gnome/recipes-gnome/gnome-desktop/gnome-desktop3_3.32.0.bb @@ -8,7 +8,11 @@ BPN = "gnome-desktop" GNOMEBASEBUILDCLASS = "meson" -inherit gnome pkgconfig upstream-version-is-even gobject-introspection +inherit gnome pkgconfig upstream-version-is-even gobject-introspection distro_features_check + +# gobject-introspection is mandatory and cannot be configured +REQUIRED_DISTRO_FEATURES = "gobject-introspection-data" +UNKNOWN_CONFIGURE_WHITELIST_append = " introspection" SRC_URI[archive.md5sum] = "e423ed6d648c6c4f9798fa9cd9ea8d99" SRC_URI[archive.sha256sum] = "a6393dc5fc29fc0652ac84c73b3da205d0b0168128c4cf6d27797a08f3d07b54" -- 2.20.1 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [PATCH 1/2] gnome-desktop3: remove gconf from DEPENDS
Modern gnome does not use gconf anymore. Signed-off-by: Andreas Müller --- meta-gnome/recipes-gnome/gnome-desktop/gnome-desktop3_3.32.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-gnome/recipes-gnome/gnome-desktop/gnome-desktop3_3.32.0.bb b/meta-gnome/recipes-gnome/gnome-desktop/gnome-desktop3_3.32.0.bb index 185a25359..c1a67bda9 100644 --- a/meta-gnome/recipes-gnome/gnome-desktop/gnome-desktop3_3.32.0.bb +++ b/meta-gnome/recipes-gnome/gnome-desktop/gnome-desktop3_3.32.0.bb @@ -15,7 +15,7 @@ SRC_URI[archive.sha256sum] = "a6393dc5fc29fc0652ac84c73b3da205d0b0168128c4cf6d27 SRC_URI += "file://gnome-desktop-thumbnail-don-t-assume-time_t-is-long.patch" -DEPENDS += "itstool-native gsettings-desktop-schemas gconf virtual/libx11 gtk+3 glib-2.0 startup-notification xkeyboard-config iso-codes udev" +DEPENDS += "itstool-native gsettings-desktop-schemas virtual/libx11 gtk+3 startup-notification xkeyboard-config iso-codes udev" inherit distro_features_check gtk-doc REQUIRED_DISTRO_FEATURES = "x11" -- 2.20.1 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-python][PATCH 5/6] python3-xxhash: Initial commit
Signed-off-by: Alistair Francis --- meta-python/recipes-devtools/python/python-xxhash.inc | 7 +++ .../recipes-devtools/python/python3-xxhash_1.3.0.bb| 2 ++ 2 files changed, 9 insertions(+) create mode 100644 meta-python/recipes-devtools/python/python-xxhash.inc create mode 100644 meta-python/recipes-devtools/python/python3-xxhash_1.3.0.bb diff --git a/meta-python/recipes-devtools/python/python-xxhash.inc b/meta-python/recipes-devtools/python/python-xxhash.inc new file mode 100644 index 0..9df4520f7 --- /dev/null +++ b/meta-python/recipes-devtools/python/python-xxhash.inc @@ -0,0 +1,7 @@ +SUMMARY = "xxhash is a Python binding for the xxHash library by Yann Collet." +SECTION = "devel/python" +LICENSE = "BSD" +LIC_FILES_CHKSUM = "file://LICENSE;md5=d2c6db5887cc6b2fac8b701d64cb8442" + +SRC_URI[md5sum] = "a4289aa01839f3ea1fb98929d9131001" +SRC_URI[sha256sum] = "fe21f23a9d05428c75461790b670f2bf15f50a632d6c171a7e7b588269c619e6" diff --git a/meta-python/recipes-devtools/python/python3-xxhash_1.3.0.bb b/meta-python/recipes-devtools/python/python3-xxhash_1.3.0.bb new file mode 100644 index 0..76bc41a11 --- /dev/null +++ b/meta-python/recipes-devtools/python/python3-xxhash_1.3.0.bb @@ -0,0 +1,2 @@ +require python-xxhash.inc +inherit pypi setuptools3 -- 2.21.0 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-multimedia][PATCH 6/6] mycroft: Initial commit
Mycroft is an open source speech assistant. It traditionally runs inside
Python virtual env and installs all of the pip and native packages and
programs that is needs at setup. This generally includes a native gcc
build for some of the binaries in the pip packages.
This patch adds Mycroft support and edits the source to remove the
Python venv usage so we can just run in standard Python world. This
allows us to use the preinstalled Python packages where avaliable and
avoid installing too much on the target at runtime. At the moment we
still require a few simple Python packages to be installed but we don't
requrie any target compilation.
Hopefully in the future we can remove all of the runtime install
requirements by adding all the Python packages to the rootFS pre-boot
and setting up the other files/directories as required during the build
process.
Signed-off-by: Alistair Francis
---
.../files/0001-Remove-python-venv.patch | 192 ++
...irements-Remove-ones-installed-by-OE.patch | 62 ++
...3-and-pip3-instead-of-python-and-pip.patch | 135
...v_setup.sh-Remove-the-git-dependency.patch | 48 +
sh-Remove-the-test-setup-dependency.patch | 31 +++
.../mycroft/files/mycroft.service | 13 ++
.../mycroft/mycroft_19.2.2.bb | 61 ++
7 files changed, 542 insertions(+)
create mode 100644
meta-multimedia/recipes-multimedia/mycroft/files/0001-Remove-python-venv.patch
create mode 100644
meta-multimedia/recipes-multimedia/mycroft/files/0002-pip-requirements-Remove-ones-installed-by-OE.patch
create mode 100644
meta-multimedia/recipes-multimedia/mycroft/files/0003-Use-python3-and-pip3-instead-of-python-and-pip.patch
create mode 100644
meta-multimedia/recipes-multimedia/mycroft/files/0004-dev_setup.sh-Remove-the-git-dependency.patch
create mode 100644
meta-multimedia/recipes-multimedia/mycroft/files/0005-dev_setup.sh-Remove-the-test-setup-dependency.patch
create mode 100644
meta-multimedia/recipes-multimedia/mycroft/files/mycroft.service
create mode 100644 meta-multimedia/recipes-multimedia/mycroft/mycroft_19.2.2.bb
diff --git
a/meta-multimedia/recipes-multimedia/mycroft/files/0001-Remove-python-venv.patch
b/meta-multimedia/recipes-multimedia/mycroft/files/0001-Remove-python-venv.patch
new file mode 100644
index 0..c03bccd3d
--- /dev/null
+++
b/meta-multimedia/recipes-multimedia/mycroft/files/0001-Remove-python-venv.patch
@@ -0,0 +1,192 @@
+From 6272f36080bd440a5825b526f4c06223c5bb9fbb Mon Sep 17 00:00:00 2001
+From: Alistair Francis
+Date: Mon, 18 Mar 2019 16:30:45 -0700
+Subject: [PATCH 1/5] Remove python venv
+
+Remove the python venv requirements and instead just use the native
+python and pip pacakges.
+
+Signed-off-by: Alistair Francis
+Upstream-Status: Inappropriate [embedded specific]
+---
+ dev_setup.sh | 36
+ start-mycroft.sh | 13 -
+ venv-activate.sh | 44 +---
+ 3 files changed, 1 insertion(+), 92 deletions(-)
+
+diff --git a/dev_setup.sh b/dev_setup.sh
+index e0b07bf25cf..aed54b2167a 100755
+--- a/dev_setup.sh
b/dev_setup.sh
+@@ -310,18 +310,6 @@ function install_deps() {
+ fi
+ }
+
+-VIRTUALENV_ROOT=${VIRTUALENV_ROOT:-"${TOP}/.venv"}
+-
+-function install_venv() {
+-${opt_python} -m venv "${VIRTUALENV_ROOT}/" --without-pip
+-# Force version of pip for reproducability, but there is nothing special
+-# about this version. Update whenever a new version is released and
+-# verified functional.
+-curl https://bootstrap.pypa.io/3.3/get-pip.py |
"${VIRTUALENV_ROOT}/bin/python" - 'pip==18.0.0'
+-# Function status depending on if pip exists
+-[ -x "${VIRTUALENV_ROOT}/bin/pip" ]
+-}
+-
+ install_deps
+
+ # Configure to use the standard commit template for
+@@ -355,15 +343,7 @@ else
+ fi
+ fi
+
+-if [ ! -x "${VIRTUALENV_ROOT}/bin/activate" ] ; then
+-if ! install_venv ; then
+-echo "Failed to set up virtualenv for mycroft, exiting setup."
+-exit 1
+-fi
+-fi
+-
+ # Start the virtual environment
+-source "${VIRTUALENV_ROOT}/bin/activate"
+ cd "${TOP}"
+
+ # Install pep8 pre-commit hook
+@@ -380,22 +360,6 @@ fi
+
+ PYTHON=$( python -c "import
sys;print('python{}.{}'.format(sys.version_info[0], sys.version_info[1]))" )
+
+-# Add mycroft-core to the virtualenv path
+-# (This is equivalent to typing 'add2virtualenv $TOP', except
+-# you can't invoke that shell function from inside a script)
+-VENV_PATH_FILE="${VIRTUALENV_ROOT}/lib/$PYTHON/site-packages/_virtualenv_path_extensions.pth"
+-if [ ! -f "$VENV_PATH_FILE" ] ; then
+-echo "import sys; sys.__plen = len(sys.path)" > "$VENV_PATH_FILE" ||
return 1
+-echo "import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:];
p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert =
p+len(new)" >> "$VENV_PATH_FILE" || return 1
+-fi
+-
+-if ! grep -q "$TOP" $VENV_PATH_FILE ; then
[oe] [meta-python][PATCH 4/6] python3-pocketsphinx: Initial commit
Signed-off-by: Alistair Francis --- .../recipes-devtools/python/python-pocketsphinx.inc | 9 + .../python/python3-pocketsphinx_0.1.0.bb | 2 ++ 2 files changed, 11 insertions(+) create mode 100644 meta-python/recipes-devtools/python/python-pocketsphinx.inc create mode 100644 meta-python/recipes-devtools/python/python3-pocketsphinx_0.1.0.bb diff --git a/meta-python/recipes-devtools/python/python-pocketsphinx.inc b/meta-python/recipes-devtools/python/python-pocketsphinx.inc new file mode 100644 index 0..4c848b6dd --- /dev/null +++ b/meta-python/recipes-devtools/python/python-pocketsphinx.inc @@ -0,0 +1,9 @@ +SUMMARY = "This package provides a python interface to CMU Sphinxbase and Pocketsphinx libraries created with SWIG and Setuptools." +SECTION = "devel/python" +LICENSE = "BSD" +LIC_FILES_CHKSUM = "file://LICENSE;md5=826ebda787eb48e78aec2624f9faba72" + +SRC_URI[md5sum] = "c0f2bfd54bc4c438c3bb64825f57d575" +SRC_URI[sha256sum] = "2cc493ed48c1301e0d2e69b137dc646c2f8caca190ef4bce61836eac96d1796f" + +DEPENDS += "swig-native" diff --git a/meta-python/recipes-devtools/python/python3-pocketsphinx_0.1.0.bb b/meta-python/recipes-devtools/python/python3-pocketsphinx_0.1.0.bb new file mode 100644 index 0..2275d1b50 --- /dev/null +++ b/meta-python/recipes-devtools/python/python3-pocketsphinx_0.1.0.bb @@ -0,0 +1,2 @@ +require python-pocketsphinx.inc +inherit pypi setuptools3 -- 2.21.0 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH 2/6] libfann: Initial commit
Use the current master branch instead of the last release in 2013.
Signed-off-by: Alistair Francis
---
meta-oe/recipes-support/libfann/libfann_git.bb | 15 +++
1 file changed, 15 insertions(+)
create mode 100644 meta-oe/recipes-support/libfann/libfann_git.bb
diff --git a/meta-oe/recipes-support/libfann/libfann_git.bb
b/meta-oe/recipes-support/libfann/libfann_git.bb
new file mode 100644
index 0..87d7902bb
--- /dev/null
+++ b/meta-oe/recipes-support/libfann/libfann_git.bb
@@ -0,0 +1,15 @@
+SUMMARY = "Fast Artificial Neural Network (FANN) Library"
+DESCRIPTION = "Fast Artificial Neural Network (FANN) Library is a free open
source neural network library, which implements multilayer artificial neural
networks in C with support for both fully connected and sparsely connected
networks."
+HOMEPAGE = "https://github.com/libfann/fann;
+SECTION = "libs/devel"
+
+LICENSE = "LGPLv2.1"
+LIC_FILES_CHKSUM = "file://LICENSE.md;md5=f14599a2f089f6ff8c97e2baa4e3d575"
+
+inherit cmake
+
+SRCREV = "${AUTOREV}"
+SRC_URI = "git://github.com/libfann/fann.git;branch=master \
+ "
+
+S = "${WORKDIR}/git"
--
2.21.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-python][PATCH 3/6] python3-pyfann2: Initial commit
Signed-off-by: Alistair Francis
---
.../recipes-devtools/python/python-fann2.inc | 9 ++
...ardcode-swig-and-fann2-binary-locati.patch | 28 +++
.../python/python3-fann2_1.1.2.bb | 4 +++
3 files changed, 41 insertions(+)
create mode 100644 meta-python/recipes-devtools/python/python-fann2.inc
create mode 100644
meta-python/recipes-devtools/python/python3-fann2/0001-setup.py-Don-t-hardcode-swig-and-fann2-binary-locati.patch
create mode 100644 meta-python/recipes-devtools/python/python3-fann2_1.1.2.bb
diff --git a/meta-python/recipes-devtools/python/python-fann2.inc
b/meta-python/recipes-devtools/python/python-fann2.inc
new file mode 100644
index 0..c415b35a9
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python-fann2.inc
@@ -0,0 +1,9 @@
+SUMMARY = "Python bindings for Fast Artificial Neural Networks 2.2.0 (FANN >=
2.2.0)"
+SECTION = "devel/python"
+LICENSE = "LGPLv2"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=c73b943dc75f6f65e007c56ac6515c8f"
+
+SRC_URI[md5sum] = "0b85b418018746d63ed66b55465697a9"
+SRC_URI[sha256sum] =
"cdca0a65ad48e08320672affe38c3dd4ea15e27821e5e1db9fa2b34299bdd41e"
+
+DEPENDS += "swig-native libfann"
diff --git
a/meta-python/recipes-devtools/python/python3-fann2/0001-setup.py-Don-t-hardcode-swig-and-fann2-binary-locati.patch
b/meta-python/recipes-devtools/python/python3-fann2/0001-setup.py-Don-t-hardcode-swig-and-fann2-binary-locati.patch
new file mode 100644
index 0..cbc838f0e
--- /dev/null
+++
b/meta-python/recipes-devtools/python/python3-fann2/0001-setup.py-Don-t-hardcode-swig-and-fann2-binary-locati.patch
@@ -0,0 +1,28 @@
+From 85307f592c7cb87af162cca4b121b874108b7754 Mon Sep 17 00:00:00 2001
+From: Alistair Francis
+Date: Tue, 2 Apr 2019 11:25:15 -0700
+Subject: [PATCH] setup.py: Don't hardcode swig and fann2 binary locations
+
+Upstream-Status: Inappropriate [configuration]
+Signed-off-by: Alistair Francis
+---
+ setup.py | 5 +
+ 1 file changed, 1 insertion(+), 4 deletions(-)
+
+diff --git a/setup.py b/setup.py
+index 37af7c7..8e416f2 100755
+--- a/setup.py
b/setup.py
+@@ -81,11 +81,8 @@ def find_swig():
+
+ def build_swig():
+ '''Run SWIG with specified parameters'''
+-print("Looking for FANN libs...")
+-find_fann()
+-print("running SWIG...")
+ swig_bin = find_swig()
+-swig_cmd = [swig_bin, '-c++', '-python', 'fann2/fann2.i']
++swig_cmd = ['swig', '-c++', '-python', 'fann2/fann2.i']
+ subprocess.Popen(swig_cmd).wait()
+
+ if "sdist" not in sys.argv:
diff --git a/meta-python/recipes-devtools/python/python3-fann2_1.1.2.bb
b/meta-python/recipes-devtools/python/python3-fann2_1.1.2.bb
new file mode 100644
index 0..a04c961f4
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python3-fann2_1.1.2.bb
@@ -0,0 +1,4 @@
+require python-fann2.inc
+inherit pypi setuptools3
+
+SRC_URI += "
file://0001-setup.py-Don-t-hardcode-swig-and-fann2-binary-locati.patch"
--
2.21.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-python][PATCH 1/6] python3-pyaudio: Initial commit
Signed-off-by: Alistair Francis
---
.../recipes-devtools/python/python-pyaudio.inc | 13 +
.../python/python3-pyaudio_0.2.11.bb| 2 ++
2 files changed, 15 insertions(+)
create mode 100644 meta-python/recipes-devtools/python/python-pyaudio.inc
create mode 100644
meta-python/recipes-devtools/python/python3-pyaudio_0.2.11.bb
diff --git a/meta-python/recipes-devtools/python/python-pyaudio.inc
b/meta-python/recipes-devtools/python/python-pyaudio.inc
new file mode 100644
index 0..0d3ddb1a5
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python-pyaudio.inc
@@ -0,0 +1,13 @@
+SUMMARY = "PyAudio provides Python bindings for PortAudio, the cross-platform
audio I/O library"
+SECTION = "devel/python"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://README;md5=288793c2b9b05bd67abbd2a8f5d144f7"
+
+PYPI_PACKAGE = "PyAudio"
+
+SRC_URI[md5sum] = "7e4c88139284033f67b4336c74eda3b8"
+SRC_URI[sha256sum] =
"93bfde30e0b64e63a46f2fd77e85c41fd51182a4a3413d9edfaf9ffaa26efb74"
+
+DEPENDS += "portaudio-v19"
+
+RDEPENDS_${PN} += "portaudio-v19"
diff --git a/meta-python/recipes-devtools/python/python3-pyaudio_0.2.11.bb
b/meta-python/recipes-devtools/python/python3-pyaudio_0.2.11.bb
new file mode 100644
index 0..abb01bf69
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python3-pyaudio_0.2.11.bb
@@ -0,0 +1,2 @@
+require python-pyaudio.inc
+inherit pypi setuptools3
--
2.21.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [PATCH 2/2] gvfs: Fix missing executable permission flags for files in libexec
At least XFCE sessions turned into unusable state [1]
[1]
http://lists.openembedded.org/pipermail/openembedded-devel/2019-April/199010.html
Signed-off-by: Andreas Müller
---
meta-gnome/recipes-gnome/gvfs/gvfs_1.40.0.bb | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/meta-gnome/recipes-gnome/gvfs/gvfs_1.40.0.bb
b/meta-gnome/recipes-gnome/gvfs/gvfs_1.40.0.bb
index 7b9a16e9e..df9fd50ea 100644
--- a/meta-gnome/recipes-gnome/gvfs/gvfs_1.40.0.bb
+++ b/meta-gnome/recipes-gnome/gvfs/gvfs_1.40.0.bb
@@ -61,8 +61,16 @@ PACKAGECONFIG[fuse] = "-Dfuse=true, -Dfuse=false, fuse"
# libcdio-paranoia recipe doesn't exist yet
PACKAGECONFIG[cdda] = "-Dcdda=true, -Dcdda=false, libcdio-paranoia"
-# Fix up permissions on polkit rules.d to work with rpm4 constraints
do_install_append() {
+# Fix up permissions on polkit rules.d to work with rpm4 constraints
chmod 700 ${D}/${datadir}/polkit-1/rules.d
chown polkitd:root ${D}/${datadir}/polkit-1/rules.d
+
+# After rebuilds (not from scracth) it can happen that the executables in
+# libexec ar missing executable permission flag. Not sure but it came up
+# during transition to meson. Looked into build files and logs but could
+# not find suspicious
+for exe in `find ${D}/${libexec}`; do
+ chmod +x $exe
+done
}
--
2.20.1
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [PATCH 1/2] libpeas: rework gobject-introspection handling
gobject-introspection is mandatory for libpeas - there is no configure option to enable or disable it. To handle properly, this patch does: * Make 'gobject-introspection-data' a required distro feature * To avoid trouble once pending patch removing 'UNKNOWN_CONFIGURE_WHITELIST_append = " --enable-introspection --disable-introspection"' are in oe-core [1] - set in recipe to avoid | libpeas-1.22.0-r0 do_configure: QA Issue: libpeas: configure was passed unrecognised options: --enable-introspection [unknown-configure-option] This does not handle MACHINE_FEATURES / qemu-usermode case but there other issues of higher priority. [1] http://lists.openembedded.org/pipermail/openembedded-core/2019-April/280711.html Signed-off-by: Andreas Müller --- meta-oe/recipes-gnome/libpeas/libpeas_1.22.0.bb | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/meta-oe/recipes-gnome/libpeas/libpeas_1.22.0.bb b/meta-oe/recipes-gnome/libpeas/libpeas_1.22.0.bb index c1ead0670..dd1b53e39 100644 --- a/meta-oe/recipes-gnome/libpeas/libpeas_1.22.0.bb +++ b/meta-oe/recipes-gnome/libpeas/libpeas_1.22.0.bb @@ -5,7 +5,11 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=4b54a1fd55a448865a0b32d41598759d" DEPENDS = "gnome-common gtk+3 intltool-native" -inherit gnomebase gobject-introspection gtk-doc gtk-icon-cache +inherit gnomebase gobject-introspection gtk-doc gtk-icon-cache distro_features_check + +# gobject-introspection is mandatory and cannot be configured +REQUIRED_DISTRO_FEATURES = "gobject-introspection-data" +UNKNOWN_CONFIGURE_WHITELIST_append = " --enable-introspection --disable-introspection" SRC_URI[archive.md5sum] = "a20dc55c3f88ad06da9491cfd7de7558" SRC_URI[archive.sha256sum] = "5b2fc0f53962b25bca131a5ec0139e6fef8e254481b6e777975f7a1d2702a962" -- 2.20.1 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] [OE-core] Git commit process question.
On Thursday, 4 April 2019 5:46:04 AM NZDT Khem Raj wrote: > On Wed, Apr 3, 2019 at 7:41 AM Tom Rini wrote: > > > > On Wed, Apr 03, 2019 at 11:30:39AM +0100, Burton, Ross wrote: > > > On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote: > > > > > The kernel does not have "upgrade foo to the latest upstream > > > > > version" commits. > > > > > > > > > > With the Automatic Upgrade Helper this is a semi-automatic task, and > > > > > most of the time there is no specific motivation other than > > > > > upgrading > > > > > to the latest upstream version. > > > > > > > > But since that's just filling in a template the body can also be a > > > > template perhaps with useful AUH data (run at ... by ... ?) ? > > > > > > Apart from making the commit message longer what does this achieve? > > > The commit already has a timestamp and author. > > > > It's an etiquette thing. Subject+Sign-off+Empty body is bad form. AUH > > updates are a form of "trivial update" that every project has. "Update > > $X from version $Y to $Z" is what a human would normally put. It's > > weird looking at git log of nothing but subject+signed-off-by. I'm not > > going to object further on this point, but I don't get it. > > if the content of subject is being repeated in body then I would > prefer an empty body > redundant information in commits should be avoided since it can create > impression that body does not have > useful information and skip reading it. We should strive to make commits > concise and useful. There is often (I won't say always, but often) something useful you can put in the commit message. If it's a recipe upgrade, you could put a pointer to the upstream changelog in it, for example. As the person doing the upgrade if your prior review of that changelog or other upstream release documentation indicated any backwards-compatibility issues or CVEs fixed then those really ought to be mentioned as well; if you're feeling especially generous you might mention highlights of any new functionality. (I have a proposal that might help us automate part of that which I've not yet fully fleshed out, hopefully one day soon I will get around to it.) The issue of empty commit messages is something I've complained about in the past, and not just about recipe upgrades. If I - as someone who is relatively familiar with OE - have to actually read beyond the shortlog / commit message to understand the basics of why a change has been made, then it's likely that the commit message wasn't good enough. Unlike other issues, once a commit goes in the message is set in stone within the git history, so if you are working on a change, *please* take a minute or two to document it adequately in the commit message so that others looking back can understand it. Thanks, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
Hi Khem,
To be honest I disabled it because I don't have much time to add ptest
stuff and I had a failure with it.
I'll try to rework that part and at least put it in a packageconfig knob as
suggested.
Thanks for review,
Vincent
Le mer. 3 avr. 2019 à 18:52, Khem Raj a écrit :
> On Wed, Apr 3, 2019 at 1:30 AM Vincent Prince
> wrote:
> >
> > Signed-off-by: Vincent Prince
> > ---
> > meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb | 6 --
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > index 9aff59c..2f99417 100644
> > --- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > +++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > @@ -4,8 +4,8 @@ LICENSE = "MIT"
> > LIC_FILES_CHKSUM = "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
> > DEPENDS = "zeromq"
> >
> > -SRCREV = "6aa3ab686e916cb0e62df7fa7d12e0b13ae9fae6"
> > -PV = "4.2.3+git${SRCPV}"
> > +SRCREV = "213da0b04ae3b4d846c9abc46bab87f86bfb9cf4"
> > +PV = "4.3.1+git${SRCPV}"
> >
> > SRC_URI = "git://github.com/zeromq/cppzmq.git"
> >
> > @@ -13,6 +13,8 @@ S = "${WORKDIR}/git"
> >
> > inherit cmake
> >
> > +EXTRA_OECMAKE = "-DCPPZMQ_BUILD_TESTS=OFF"
> > +
>
> explaining why tests are disabled would be helpful for future changes
> where someone might
> want to enable it and if its an optimization then turn it into
> packageconfig knob.
>
> > PACKAGES = "${PN}-dev"
> >
> > RDEPENDS_${PN}-dev = "zeromq-dev"
> > --
> > 2.7.4
> >
> > --
> > ___
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-python][PATCH] python*-requests: Update 2.20.1 -> 2.21.0
Signed-off-by: Fabio Berton
---
meta-python/recipes-devtools/python/python-requests.inc | 4 ++--
.../{python-requests_2.20.1.bb => python-requests_2.21.0.bb} | 0
...{python3-requests_2.20.1.bb => python3-requests_2.21.0.bb} | 0
3 files changed, 2 insertions(+), 2 deletions(-)
rename meta-python/recipes-devtools/python/{python-requests_2.20.1.bb =>
python-requests_2.21.0.bb} (100%)
rename meta-python/recipes-devtools/python/{python3-requests_2.20.1.bb =>
python3-requests_2.21.0.bb} (100%)
diff --git a/meta-python/recipes-devtools/python/python-requests.inc
b/meta-python/recipes-devtools/python/python-requests.inc
index 0401ee448..e6337cb32 100644
--- a/meta-python/recipes-devtools/python/python-requests.inc
+++ b/meta-python/recipes-devtools/python/python-requests.inc
@@ -5,8 +5,8 @@ LIC_FILES_CHKSUM =
"file://LICENSE;md5=a8d5a1d1c2d53025e2282c511033f6f7"
FILESEXTRAPATHS_prepend := "${THISDIR}/python-requests:"
-SRC_URI[md5sum] = "2918817ea4688f4ea21cb4b11e353448"
-SRC_URI[sha256sum] =
"ea881206e59f41dbd0bd445437d792e43906703fff75ca8ff43ccdb11f33f263"
+SRC_URI[md5sum] = "1bcd0e0977c3f8db1848ba0e2b7ab904"
+SRC_URI[sha256sum] =
"502a824f31acdacb3a35b6690b5fbf0bc41d63a24a45c4004352b0242707598e"
inherit pypi
diff --git a/meta-python/recipes-devtools/python/python-requests_2.20.1.bb
b/meta-python/recipes-devtools/python/python-requests_2.21.0.bb
similarity index 100%
rename from meta-python/recipes-devtools/python/python-requests_2.20.1.bb
rename to meta-python/recipes-devtools/python/python-requests_2.21.0.bb
diff --git a/meta-python/recipes-devtools/python/python3-requests_2.20.1.bb
b/meta-python/recipes-devtools/python/python3-requests_2.21.0.bb
similarity index 100%
rename from meta-python/recipes-devtools/python/python3-requests_2.20.1.bb
rename to meta-python/recipes-devtools/python/python3-requests_2.21.0.bb
--
2.20.1
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
On Wed, Apr 3, 2019 at 1:30 AM Vincent Prince
wrote:
>
> Signed-off-by: Vincent Prince
> ---
> meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> index 9aff59c..2f99417 100644
> --- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> +++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> @@ -4,8 +4,8 @@ LICENSE = "MIT"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
> DEPENDS = "zeromq"
>
> -SRCREV = "6aa3ab686e916cb0e62df7fa7d12e0b13ae9fae6"
> -PV = "4.2.3+git${SRCPV}"
> +SRCREV = "213da0b04ae3b4d846c9abc46bab87f86bfb9cf4"
> +PV = "4.3.1+git${SRCPV}"
>
> SRC_URI = "git://github.com/zeromq/cppzmq.git"
>
> @@ -13,6 +13,8 @@ S = "${WORKDIR}/git"
>
> inherit cmake
>
> +EXTRA_OECMAKE = "-DCPPZMQ_BUILD_TESTS=OFF"
> +
explaining why tests are disabled would be helpful for future changes
where someone might
want to enable it and if its an optimization then turn it into
packageconfig knob.
> PACKAGES = "${PN}-dev"
>
> RDEPENDS_${PN}-dev = "zeromq-dev"
> --
> 2.7.4
>
> --
> ___
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] Git commit process question.
On Wed, Apr 3, 2019 at 7:41 AM Tom Rini wrote: > > On Wed, Apr 03, 2019 at 11:30:39AM +0100, Burton, Ross wrote: > > On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote: > > > > The kernel does not have "upgrade foo to the latest upstream version" > > > > commits. > > > > > > > > With the Automatic Upgrade Helper this is a semi-automatic task, and > > > > most of the time there is no specific motivation other than upgrading > > > > to the latest upstream version. > > > > > > But since that's just filling in a template the body can also be a > > > template perhaps with useful AUH data (run at ... by ... ?) ? > > > > Apart from making the commit message longer what does this achieve? > > The commit already has a timestamp and author. > > It's an etiquette thing. Subject+Sign-off+Empty body is bad form. AUH > updates are a form of "trivial update" that every project has. "Update > $X from version $Y to $Z" is what a human would normally put. It's > weird looking at git log of nothing but subject+signed-off-by. I'm not > going to object further on this point, but I don't get it. if the content of subject is being repeated in body then I would prefer an empty body redundant information in commits should be avoided since it can create impression that body does not have useful information and skip reading it. We should strive to make commits concise and useful. -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] s-suite: push SRCREV to version 3.1
Hi,
have you guys had time to look into this?
Thanks,
Paolo
> Il giorno 28 mar 2019, alle ore 23:04, Paolo Valente
> ha scritto:
>
> Signed-off-by: Paolo Valente
> ---
> meta-oe/recipes-benchmark/s-suite/s-suite_git.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-oe/recipes-benchmark/s-suite/s-suite_git.bb
> b/meta-oe/recipes-benchmark/s-suite/s-suite_git.bb
> index 8bd0afc49..47d21d36c 100644
> --- a/meta-oe/recipes-benchmark/s-suite/s-suite_git.bb
> +++ b/meta-oe/recipes-benchmark/s-suite/s-suite_git.bb
> @@ -2,7 +2,7 @@ SUMMARY = "Small collection of benchmarks for storage I/O"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=b529aaa6a0c50f15d29f89609b5c22f3"
>
> -SRCREV = "e2727f70ed79b5461689c062a4a66a87f1adb4ce"
> +SRCREV = "d05006865f68829fa7603bdb92bd51649f5ba1b6"
> PV = "0.0+git${SRCPV}"
> SRC_URI = "git://github.com/Algodev-github/S.git;protocol=https;branch=master"
>
> --
> 2.20.1
>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] Git commit process question.
On Wed, Apr 03, 2019 at 11:30:39AM +0100, Burton, Ross wrote: > On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote: > > > The kernel does not have "upgrade foo to the latest upstream version" > > > commits. > > > > > > With the Automatic Upgrade Helper this is a semi-automatic task, and > > > most of the time there is no specific motivation other than upgrading > > > to the latest upstream version. > > > > But since that's just filling in a template the body can also be a > > template perhaps with useful AUH data (run at ... by ... ?) ? > > Apart from making the commit message longer what does this achieve? > The commit already has a timestamp and author. It's an etiquette thing. Subject+Sign-off+Empty body is bad form. AUH updates are a form of "trivial update" that every project has. "Update $X from version $Y to $Z" is what a human would normally put. It's weird looking at git log of nothing but subject+signed-off-by. I'm not going to object further on this point, but I don't get it. -- Tom signature.asc Description: PGP signature -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH v2 1/3] zeromq: bump version 4.2.5 => 4.3.1
Also, use cmake instead of autotools to build it.
Signed-off-by: Vincent Prince
---
.../recipes-connectivity/zeromq/zeromq_4.2.5.bb| 32 --
.../recipes-connectivity/zeromq/zeromq_4.3.1.bb| 26 ++
2 files changed, 26 insertions(+), 32 deletions(-)
delete mode 100644 meta-oe/recipes-connectivity/zeromq/zeromq_4.2.5.bb
create mode 100644 meta-oe/recipes-connectivity/zeromq/zeromq_4.3.1.bb
diff --git a/meta-oe/recipes-connectivity/zeromq/zeromq_4.2.5.bb
b/meta-oe/recipes-connectivity/zeromq/zeromq_4.2.5.bb
deleted file mode 100644
index 356348b..000
--- a/meta-oe/recipes-connectivity/zeromq/zeromq_4.2.5.bb
+++ /dev/null
@@ -1,32 +0,0 @@
-DESCRIPTION = "ZeroMQ looks like an embeddable networking library but acts
like a concurrency framework"
-HOMEPAGE = "http://www.zeromq.org;
-LICENSE = "LGPLv3+"
-LIC_FILES_CHKSUM = "file://COPYING.LESSER;md5=d5311495d952062e0e4fbba39cbf3de1"
-
-PACKAGECONFIG ??= "libsodium"
-PACKAGECONFIG[libsodium] = "--with-libsodium, --without-libsodium, libsodium"
-
-SRC_URI =
"http://github.com/zeromq/libzmq/releases/download/v${PV}/zeromq-${PV}.tar.gz \
-file://run-ptest \
-"
-SRC_URI[md5sum] = "a1c95b34384257e986842f4d006957b8"
-SRC_URI[sha256sum] =
"cc9090ba35713d59bb2f7d7965f877036c49c5558ea0c290b0dcc6f2a17e489f"
-
-S = "${WORKDIR}/zeromq-${PV}"
-
-#Uncomment to choose polling system manually. valid values are kqueue, epoll,
devpoll, poll or select
-#EXTRA_OECONF += "--with-poller=kqueue"
-#CFLAGS_append = " -O0"
-#CXXFLAGS_append = " -O0"
-
-inherit autotools ptest pkgconfig
-
-do_compile_ptest () {
-echo 'buildtest-TESTS: $(check_PROGRAMS)' >> ${B}/Makefile
-oe_runmake buildtest-TESTS
-}
-
-do_install_ptest () {
-install -d ${D}${PTEST_PATH}/tests
-install -m 0755 ${B}/tests/.libs/test_* ${D}${PTEST_PATH}/tests
-}
diff --git a/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.1.bb
b/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.1.bb
new file mode 100644
index 000..6e13376
--- /dev/null
+++ b/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.1.bb
@@ -0,0 +1,26 @@
+DESCRIPTION = "ZeroMQ looks like an embeddable networking library but acts
like a concurrency framework"
+HOMEPAGE = "http://www.zeromq.org;
+LICENSE = "LGPLv3+"
+LIC_FILES_CHKSUM = "file://COPYING.LESSER;md5=d5311495d952062e0e4fbba39cbf3de1"
+
+PACKAGECONFIG ??= "libsodium"
+PACKAGECONFIG[libsodium] = "-DWITH_LIBSODIUM=ON,-DWITH_LIBSODIUM=OFF,
libsodium"
+
+SRC_URI =
"http://github.com/zeromq/libzmq/releases/download/v${PV}/zeromq-${PV}.tar.gz \
+file://run-ptest \
+"
+SRC_URI[md5sum] = "64cbf3577afdbfda30358bc757a6ac83"
+SRC_URI[sha256sum] =
"bcbabe1e2c7d0eec4ed612e10b94b112dd5f06fcefa994a0c79a45d835cd21eb"
+
+inherit cmake ptest pkgconfig
+
+EXTRA_OECMAKE = "${@bb.utils.contains('PTEST_ENABLED', '1',
'-DBUILD_TESTS=ON', '-DBUILD_TESTS=OFF', d)} \
+ -DCMAKE_SKIP_RPATH=ON \
+"
+
+do_install_ptest () {
+install -d ${D}${PTEST_PATH}/tests
+install -m 0755 ${B}/bin/test_* ${D}${PTEST_PATH}/tests
+}
+
+FILES_${PN}-doc += "${datadir}/zmq/*.txt"
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH v2 2/3] cppzmq: bump version 4.2.3 => 4.3.1
Signed-off-by: Vincent Prince
---
Changes in v2:
- Remove git SRCPV from PV
meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
index 9aff59c..95b5215 100644
--- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
+++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
@@ -4,8 +4,8 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
DEPENDS = "zeromq"
-SRCREV = "6aa3ab686e916cb0e62df7fa7d12e0b13ae9fae6"
-PV = "4.2.3+git${SRCPV}"
+SRCREV = "213da0b04ae3b4d846c9abc46bab87f86bfb9cf4"
+PV = "4.3.1"
SRC_URI = "git://github.com/zeromq/cppzmq.git"
@@ -13,6 +13,8 @@ S = "${WORKDIR}/git"
inherit cmake
+EXTRA_OECMAKE = "-DCPPZMQ_BUILD_TESTS=OFF"
+
PACKAGES = "${PN}-dev"
RDEPENDS_${PN}-dev = "zeromq-dev"
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH v2 3/3] czmq: bump version 4.1.1 => 4.2.0
Also, add curl and systemd to PACKAGECONFIG
Signed-off-by: Vincent Prince
---
Changes in v2:
- Remove unnecessary 0001-Problem-out-of-date-with-zproject.patch file
.../zeromq/{czmq_4.1.1.bb => czmq_4.2.0.bb}| 18 ++---
.../0001-Problem-out-of-date-with-zproject.patch | 31 --
2 files changed, 9 insertions(+), 40 deletions(-)
rename meta-oe/recipes-connectivity/zeromq/{czmq_4.1.1.bb => czmq_4.2.0.bb}
(56%)
delete mode 100644
meta-oe/recipes-connectivity/zeromq/files/0001-Problem-out-of-date-with-zproject.patch
diff --git a/meta-oe/recipes-connectivity/zeromq/czmq_4.1.1.bb
b/meta-oe/recipes-connectivity/zeromq/czmq_4.2.0.bb
similarity index 56%
rename from meta-oe/recipes-connectivity/zeromq/czmq_4.1.1.bb
rename to meta-oe/recipes-connectivity/zeromq/czmq_4.2.0.bb
index f2db004..4ec1c04 100644
--- a/meta-oe/recipes-connectivity/zeromq/czmq_4.1.1.bb
+++ b/meta-oe/recipes-connectivity/zeromq/czmq_4.2.0.bb
@@ -1,15 +1,13 @@
-DESCRIPTION = "C bindings for ZeroMQ"
-HOMEPAGE = "http://www.zeromq.org;
+DESCRIPTION = "High-level C binding for 0MQ"
+HOMEPAGE = "http://czmq.zeromq.org/;
LICENSE = "MPL-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=9741c346eef56131163e13b9db1241b3"
DEPENDS = "zeromq"
-SRC_URI =
"https://github.com/zeromq/czmq/releases/download/v${PV}/czmq-${PV}.tar.gz \
-file://0001-Problem-out-of-date-with-zproject.patch \
-"
+SRC_URI =
"https://github.com/zeromq/czmq/releases/download/v${PV}/czmq-${PV}.tar.gz;
-SRC_URI[md5sum] = "6d3a6fdd25c2bb29897c53670dce97bf"
-SRC_URI[sha256sum] =
"f00ff419881dc2a05d0686c8467cd89b4882677fc56f31c0e2cc81c134cbb0c0"
+SRC_URI[md5sum] = "7e09997db6ac3b25e8ed104053040722"
+SRC_URI[sha256sum] =
"cfab29c2b3cc8a845749758a51e1dd5f5160c1ef57e2a41ea96e4c2dcc8feceb"
inherit cmake
@@ -17,14 +15,16 @@ PACKAGES = "lib${BPN} lib${BPN}-dev lib${BPN}-staticdev
${PN} ${PN}-dbg"
FILES_${PN} = "${bindir}/*"
FILES_lib${BPN} = "${libdir}/*.so.*"
-FILES_lib${BPN}-dev = "${libdir}/*.so ${libdir}/pkgconfig ${includedir}"
+FILES_lib${BPN}-dev = "${libdir}/*.so ${libdir}/pkgconfig ${includedir}
${datadir}/cmake"
FILES_lib${BPN}-staticdev = "${libdir}/lib*.a"
RDEPENDS_lib${BPN}-dev = "zeromq-dev"
-PACKAGECONFIG ??= "lz4 uuid"
+PACKAGECONFIG ??= "lz4 uuid curl ${@bb.utils.filter('DISTRO_FEATURES',
'systemd', d)}"
PACKAGECONFIG[lz4] = ",-DCMAKE_DISABLE_FIND_PACKAGE_lz4=TRUE,lz4"
PACKAGECONFIG[uuid] = ",-DCMAKE_DISABLE_FIND_PACKAGE_uuid=TRUE,util-linux"
+PACKAGECONFIG[curl] = ",-DCMAKE_DISABLE_FIND_PACKAGE_libcurl=TRUE,curl"
+PACKAGECONFIG[systemd] = ",-DCMAKE_DISABLE_FIND_PACKAGE_systemd=TRUE,systemd"
BBCLASSEXTEND = "nativesdk"
diff --git
a/meta-oe/recipes-connectivity/zeromq/files/0001-Problem-out-of-date-with-zproject.patch
b/meta-oe/recipes-connectivity/zeromq/files/0001-Problem-out-of-date-with-zproject.patch
deleted file mode 100644
index 5f5702c..000
---
a/meta-oe/recipes-connectivity/zeromq/files/0001-Problem-out-of-date-with-zproject.patch
+++ /dev/null
@@ -1,31 +0,0 @@
-From d155ffd33630f80b23c31b3a6e01da221dd9bd13 Mon Sep 17 00:00:00 2001
-From: Luca Boccassi
-Date: Fri, 30 Mar 2018 16:36:22 +0100
-Subject: [PATCH] Problem: out of date with zproject
-
-Upstream-Status: backport
-Signed-off-by: Adrian Bunk
-
-diff --git a/CMakeLists.txt b/CMakeLists.txt
-index a3b81722..4f203461 100644
a/CMakeLists.txt
-+++ b/CMakeLists.txt
-@@ -38,7 +38,7 @@ if (NOT CMAKE_BUILD_TYPE)
- OUTPUT_STRIP_TRAILING_WHITESPACE
- )
- message(STATUS "git workspace root [${git_result}]: ${git_root}")
--if ( "${git_result}" == "0" )
-+if ( "${git_result}" STREQUAL "0" )
- set (CMAKE_BUILD_TYPE Debug)
- else ()
- set (CMAKE_BUILD_TYPE Release)
-@@ -608,7 +608,7 @@ add_custom_command(
- TARGET distclean
- )
-
--include(ClangFormat)
-+include(ClangFormat OPTIONAL)
-
-
- # summary
-
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH v2 0/3] Bump zeromq libraries versions
These patches are intended to bump zeromq libraries to latest stable releases
including:
- libzmq
- czmq
- cppzmq
Vincent Prince (3):
zeromq: bump version 4.2.5 => 4.3.1
cppzmq: bump version 4.2.3 => 4.3.1
czmq: bump version 4.1.1 => 4.2.0
meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb | 6 ++--
.../zeromq/{czmq_4.1.1.bb => czmq_4.2.0.bb}| 18 ++--
.../0001-Problem-out-of-date-with-zproject.patch | 31 -
.../recipes-connectivity/zeromq/zeromq_4.2.5.bb| 32 --
.../recipes-connectivity/zeromq/zeromq_4.3.1.bb| 26 ++
5 files changed, 39 insertions(+), 74 deletions(-)
rename meta-oe/recipes-connectivity/zeromq/{czmq_4.1.1.bb => czmq_4.2.0.bb}
(56%)
delete mode 100644
meta-oe/recipes-connectivity/zeromq/files/0001-Problem-out-of-date-with-zproject.patch
delete mode 100644 meta-oe/recipes-connectivity/zeromq/zeromq_4.2.5.bb
create mode 100644 meta-oe/recipes-connectivity/zeromq/zeromq_4.3.1.bb
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
On Wed, Apr 03, 2019 at 02:31:13PM +0200, Vincent Prince wrote:
> Martin,
>
> Thanks for precisions, I will update PV to 4.3.1 in V2
> By the way, it's first time I submit a patch series, should changelog be
> in each patch for should I use --cover option to put them all in 0/3?
If you mean changelog for review changes made to individual commits,
then it's best to include them in commit message, but bellow --- so that
it doesn't end in the final commit message once it's applied.
Cover letter is useful to describe reasoning behind the whole series,
but each commit should make sense individually (especially because cover
letter doesn't end in git history).
Regards,
>
> Best regards
>
> Le mer. 3 avr. 2019 à 14:03, Martin Jansa a écrit :
>
> > On Wed, Apr 03, 2019 at 01:36:24PM +0200, Vincent Prince wrote:
> > > Adrien,
> > >
> > > What I'm not sure to understand is in which case we use "_git.bb"
> > instead
> > > of having PV in filename.
> >
> > The PV in filename is just another way for setting PV variable (instead
> > of setting it inside the recipe). This isn't relevant to what Adrian
> > requested and I would keep the filename as is.
> >
> > > If we use a release version, shouldn't we point to
> > > https://github.com/zeromq/cppzmq/archive/v4.3.0.tar.gz?
> >
> > Definitely don't use github archives, they are regenerated from time to
> > time with different checksums, either you can use developer uploaded
> > tarballs (some projects on github provides them as well) or use git
> > fetcher with the SRCREV pointing the the tag.
> >
> > > And if we use git version, shouldn't we specify git commit hash to remove
> > > any ambiguity between PV and SRCREV?
> >
> > With git bitbake fetcher (git:// in SRC_URI) you always need to specify
> > SRCREV, because that's the only thing which defines what "version" of
> > the source will be fetched.
> >
> > PV in this case is only to give this SRCREV some human readable (and
> > sortable) versioning scheme. And that's what users will see when
> > installing/upgrading the built packages, so it's important to set it
> > correctly.
> >
> > +git${SRCPV} in PV is usually used to signify that the SRCREV points to
> > commit a bit newer than the "base version" in this case 4.3.1 and in
> > this case this +git${SRCPV} is unnecessary if the SRCREV matches exactly
> > with 4.3.1 tag.
> >
> > > Do you know any convention is specified somewhere?
> >
> > I don't think it's spelled anywhere in wiki.
> >
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
Martin,
Thanks for precisions, I will update PV to 4.3.1 in V2
By the way, it's first time I submit a patch series, should changelog be
in each patch for should I use --cover option to put them all in 0/3?
Best regards
Le mer. 3 avr. 2019 à 14:03, Martin Jansa a écrit :
> On Wed, Apr 03, 2019 at 01:36:24PM +0200, Vincent Prince wrote:
> > Adrien,
> >
> > What I'm not sure to understand is in which case we use "_git.bb"
> instead
> > of having PV in filename.
>
> The PV in filename is just another way for setting PV variable (instead
> of setting it inside the recipe). This isn't relevant to what Adrian
> requested and I would keep the filename as is.
>
> > If we use a release version, shouldn't we point to
> > https://github.com/zeromq/cppzmq/archive/v4.3.0.tar.gz?
>
> Definitely don't use github archives, they are regenerated from time to
> time with different checksums, either you can use developer uploaded
> tarballs (some projects on github provides them as well) or use git
> fetcher with the SRCREV pointing the the tag.
>
> > And if we use git version, shouldn't we specify git commit hash to remove
> > any ambiguity between PV and SRCREV?
>
> With git bitbake fetcher (git:// in SRC_URI) you always need to specify
> SRCREV, because that's the only thing which defines what "version" of
> the source will be fetched.
>
> PV in this case is only to give this SRCREV some human readable (and
> sortable) versioning scheme. And that's what users will see when
> installing/upgrading the built packages, so it's important to set it
> correctly.
>
> +git${SRCPV} in PV is usually used to signify that the SRCREV points to
> commit a bit newer than the "base version" in this case 4.3.1 and in
> this case this +git${SRCPV} is unnecessary if the SRCREV matches exactly
> with 4.3.1 tag.
>
> > Do you know any convention is specified somewhere?
>
> I don't think it's spelled anywhere in wiki.
>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
On Wed, Apr 03, 2019 at 01:36:24PM +0200, Vincent Prince wrote:
> Adrien,
>
> What I'm not sure to understand is in which case we use "_git.bb" instead
> of having PV in filename.
The PV in filename is just another way for setting PV variable (instead
of setting it inside the recipe). This isn't relevant to what Adrian
requested and I would keep the filename as is.
> If we use a release version, shouldn't we point to
> https://github.com/zeromq/cppzmq/archive/v4.3.0.tar.gz?
Definitely don't use github archives, they are regenerated from time to
time with different checksums, either you can use developer uploaded
tarballs (some projects on github provides them as well) or use git
fetcher with the SRCREV pointing the the tag.
> And if we use git version, shouldn't we specify git commit hash to remove
> any ambiguity between PV and SRCREV?
With git bitbake fetcher (git:// in SRC_URI) you always need to specify
SRCREV, because that's the only thing which defines what "version" of
the source will be fetched.
PV in this case is only to give this SRCREV some human readable (and
sortable) versioning scheme. And that's what users will see when
installing/upgrading the built packages, so it's important to set it
correctly.
+git${SRCPV} in PV is usually used to signify that the SRCREV points to
commit a bit newer than the "base version" in this case 4.3.1 and in
this case this +git${SRCPV} is unnecessary if the SRCREV matches exactly
with 4.3.1 tag.
> Do you know any convention is specified somewhere?
I don't think it's spelled anywhere in wiki.
signature.asc
Description: Digital signature
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [yocto] [OE-core] Git commit process question.
On 4/3/19 3:38 AM, Alexander Kanavin wrote: > Just to make clear, the AUH workflow does require the maintainer to > sign off and edit a commit message via 'git commit -s --reset-author > --amend' for every commit, Not sure if this a requirement anymore. Most of my packages got updated by other folks this time around. Hard to say if the AUH played a part or are folks now using the devtool check. > so AUH does not get in the way of useful > commit messages. There was talk of using the AUH to fast track updates that pass the process so in that case the message would be whatever the AUH provides - armin > > Alex > > On Wed, 3 Apr 2019 at 12:31, Burton, Ross wrote: >> On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote: >> pr The kernel does not have "upgrade foo to the latest upstream version" commits. With the Automatic Upgrade Helper this is a semi-automatic task, and most of the time there is no specific motivation other than upgrading to the latest upstream version. >>> But since that's just filling in a template the body can also be a >>> template perhaps with useful AUH data (run at ... by ... ?) ? >> Apart from making the commit message longer what does this achieve? >> The commit already has a timestamp and author. >> >> Ross >> -- >> ___ >> Openembedded-core mailing list >> openembedded-c...@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
Adrien,
What I'm not sure to understand is in which case we use "_git.bb" instead
of having PV in filename.
If we use a release version, shouldn't we point to
https://github.com/zeromq/cppzmq/archive/v4.3.0.tar.gz?
And if we use git version, shouldn't we specify git commit hash to remove
any ambiguity between PV and SRCREV?
Do you know any convention is specified somewhere?
Regards,
Vincent
Le mer. 3 avr. 2019 à 13:15, Adrian Bunk a écrit :
> On Wed, Apr 03, 2019 at 12:42:13PM +0200, Vincent Prince wrote:
> > Then, it would need to rename cppzmq_git.bb into cppzmq_4.3.1.git or
> can we
> > just remove +git${SRCPV} part of PV?
> >
> > In following threads it seems first option should be chosen?
> >
> https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg120575.html
> >...
>
> That is about putting PV in the recipe filename instead of "git",
> in this case the discussion would be cppzmq_git.bb versus cppzmq_4.3.1.bb
>
> I am not aware of anyone arguing against PV having a proper
> version (without +git) for a release.
>
> > Le mer. 3 avr. 2019 à 10:56, Adrian Bunk a écrit :
> > > On Wed, Apr 03, 2019 at 10:28:42AM +0200, Vincent Prince wrote:
> >...
> > > > diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > > b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > > > index 9aff59c..2f99417 100644
> > > > --- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > > > +++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > > > @@ -4,8 +4,8 @@ LICENSE = "MIT"
> > > > LIC_FILES_CHKSUM =
> "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
> > > > DEPENDS = "zeromq"
> > > >
> > > > -SRCREV = "6aa3ab686e916cb0e62df7fa7d12e0b13ae9fae6"
> > > > -PV = "4.2.3+git${SRCPV}"
> > > > +SRCREV = "213da0b04ae3b4d846c9abc46bab87f86bfb9cf4"
> > > > +PV = "4.3.1+git${SRCPV}"
> > > >...
> > >
> > > These are the actual releases, PV should not say +git${SRCPV}
> > > for them.
> > >
> > > Not a bug you introduced, but can be fixed now.
> > >
> > > cu
> > > Adrian
>
> cu
> Adrian
>
> --
>
>"Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
>"Only a promise," Lao Er said.
>Pearl S. Buck - Dragon Seed
>
>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
On Wed, Apr 03, 2019 at 12:42:13PM +0200, Vincent Prince wrote:
> Then, it would need to rename cppzmq_git.bb into cppzmq_4.3.1.git or can we
> just remove +git${SRCPV} part of PV?
>
> In following threads it seems first option should be chosen?
> https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg120575.html
>...
That is about putting PV in the recipe filename instead of "git",
in this case the discussion would be cppzmq_git.bb versus cppzmq_4.3.1.bb
I am not aware of anyone arguing against PV having a proper
version (without +git) for a release.
> Le mer. 3 avr. 2019 à 10:56, Adrian Bunk a écrit :
> > On Wed, Apr 03, 2019 at 10:28:42AM +0200, Vincent Prince wrote:
>...
> > > diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > > index 9aff59c..2f99417 100644
> > > --- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > > +++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > > @@ -4,8 +4,8 @@ LICENSE = "MIT"
> > > LIC_FILES_CHKSUM = "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
> > > DEPENDS = "zeromq"
> > >
> > > -SRCREV = "6aa3ab686e916cb0e62df7fa7d12e0b13ae9fae6"
> > > -PV = "4.2.3+git${SRCPV}"
> > > +SRCREV = "213da0b04ae3b4d846c9abc46bab87f86bfb9cf4"
> > > +PV = "4.3.1+git${SRCPV}"
> > >...
> >
> > These are the actual releases, PV should not say +git${SRCPV}
> > for them.
> >
> > Not a bug you introduced, but can be fixed now.
> >
> > cu
> > Adrian
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe] libsocketcan: update to 0.0.11
Signed-off-by: Oleksandr Kravchuk
---
.../{libsocketcan_0.0.10.bb => libsocketcan_0.0.11.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-extended/socketcan/{libsocketcan_0.0.10.bb =>
libsocketcan_0.0.11.bb} (88%)
diff --git a/meta-oe/recipes-extended/socketcan/libsocketcan_0.0.10.bb
b/meta-oe/recipes-extended/socketcan/libsocketcan_0.0.11.bb
similarity index 88%
rename from meta-oe/recipes-extended/socketcan/libsocketcan_0.0.10.bb
rename to meta-oe/recipes-extended/socketcan/libsocketcan_0.0.11.bb
index 60ca58016..0debe47e0 100644
--- a/meta-oe/recipes-extended/socketcan/libsocketcan_0.0.10.bb
+++ b/meta-oe/recipes-extended/socketcan/libsocketcan_0.0.11.bb
@@ -5,7 +5,7 @@ SECTION = "libs/network"
LICENSE = "LGPLv2.1"
LIC_FILES_CHKSUM =
"file://src/libsocketcan.c;beginline=3;endline=17;md5=97e38adced4385d8fba1ae2437cedee1"
-SRCREV = "51f1610160a1707f026f8c2d714a6f7aa3ca232b"
+SRCREV = "0ff01ae7e4d271a7b81241e7a7026bfcea0add3f"
SRC_URI = "git://git.pengutronix.de/git/tools/libsocketcan.git;protocol=git"
--
2.17.1
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe] can-isotp: bump to latest git revision
Signed-off-by: Oleksandr Kravchuk
---
meta-oe/recipes-extended/socketcan/can-isotp_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-oe/recipes-extended/socketcan/can-isotp_git.bb
b/meta-oe/recipes-extended/socketcan/can-isotp_git.bb
index 6ce3cab11..2cf2307b1 100644
--- a/meta-oe/recipes-extended/socketcan/can-isotp_git.bb
+++ b/meta-oe/recipes-extended/socketcan/can-isotp_git.bb
@@ -1,9 +1,9 @@
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=72d977d697c3c05830fdff00a7448931"
-SRCREV = "6003f9997587e6a563cebf1f246bcd0eb6deff3d"
PV = "1.0+git${SRCPV}"
SRC_URI = "git://github.com/hartkopp/can-isotp.git;protocol=https"
+SRCREV = "78084ded1916da4d41a6a2f2bb61fad3d74b7cce"
S = "${WORKDIR}/git"
--
2.17.1
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe] can-utils: bump to latest stable v2018.02.0
v2018.02.0 is the latest stable release at the moment.
License header was moved due to SPDX-License-Identifier being added to
the file.
Signed-off-by: Oleksandr Kravchuk
---
meta-oe/recipes-extended/socketcan/can-utils_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-oe/recipes-extended/socketcan/can-utils_git.bb
b/meta-oe/recipes-extended/socketcan/can-utils_git.bb
index a2d62c366..66717e9be 100644
--- a/meta-oe/recipes-extended/socketcan/can-utils_git.bb
+++ b/meta-oe/recipes-extended/socketcan/can-utils_git.bb
@@ -1,12 +1,12 @@
SUMMARY = "Linux CAN network development utilities"
DESCRIPTION = "Linux CAN network development"
LICENSE = "GPLv2 & BSD-3-Clause"
-LIC_FILES_CHKSUM =
"file://include/linux/can.h;endline=43;md5=390a2c9a3c5e3595a069ac1436553ee7"
+LIC_FILES_CHKSUM =
"file://include/linux/can.h;beginline=2;endline=44;md5=390a2c9a3c5e3595a069ac1436553ee7"
DEPENDS = "libsocketcan"
SRC_URI = "git://github.com/linux-can/${BPN}.git;protocol=git;branch=master"
-SRCREV = "4c8fb05cb4d6ddcd67299008db54af423f86fd05"
+SRCREV = "c5fd57df344710cbe7363079504de5d6f6a2e79d"
PV = "0.0+gitr${SRCPV}"
--
2.17.1
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
I mean
https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg121560.html
Le mer. 3 avr. 2019 à 12:42, Vincent Prince a
écrit :
> Then, it would need to rename cppzmq_git.bb into cppzmq_4.3.1.git or can
> we just remove +git${SRCPV} part of PV?
>
> In following threads it seems first option should be chosen?
>
> https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg120575.html
>
> https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg121561.html
>
> Le mer. 3 avr. 2019 à 10:56, Adrian Bunk a écrit :
>
>> On Wed, Apr 03, 2019 at 10:28:42AM +0200, Vincent Prince wrote:
>> > Signed-off-by: Vincent Prince
>> > ---
>> > meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb | 6 --
>> > 1 file changed, 4 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
>> b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
>> > index 9aff59c..2f99417 100644
>> > --- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
>> > +++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
>> > @@ -4,8 +4,8 @@ LICENSE = "MIT"
>> > LIC_FILES_CHKSUM =
>> "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
>> > DEPENDS = "zeromq"
>> >
>> > -SRCREV = "6aa3ab686e916cb0e62df7fa7d12e0b13ae9fae6"
>> > -PV = "4.2.3+git${SRCPV}"
>> > +SRCREV = "213da0b04ae3b4d846c9abc46bab87f86bfb9cf4"
>> > +PV = "4.3.1+git${SRCPV}"
>> >...
>>
>> These are the actual releases, PV should not say +git${SRCPV}
>> for them.
>>
>> Not a bug you introduced, but can be fixed now.
>>
>> cu
>> Adrian
>>
>> --
>>
>>"Is there not promise of rain?" Ling Tan asked suddenly out
>> of the darkness. There had been need of rain for many days.
>>"Only a promise," Lao Er said.
>>Pearl S. Buck - Dragon Seed
>>
>>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
Then, it would need to rename cppzmq_git.bb into cppzmq_4.3.1.git or can we
just remove +git${SRCPV} part of PV?
In following threads it seems first option should be chosen?
https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg120575.html
https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg121561.html
Le mer. 3 avr. 2019 à 10:56, Adrian Bunk a écrit :
> On Wed, Apr 03, 2019 at 10:28:42AM +0200, Vincent Prince wrote:
> > Signed-off-by: Vincent Prince
> > ---
> > meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb | 6 --
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > index 9aff59c..2f99417 100644
> > --- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > +++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> > @@ -4,8 +4,8 @@ LICENSE = "MIT"
> > LIC_FILES_CHKSUM = "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
> > DEPENDS = "zeromq"
> >
> > -SRCREV = "6aa3ab686e916cb0e62df7fa7d12e0b13ae9fae6"
> > -PV = "4.2.3+git${SRCPV}"
> > +SRCREV = "213da0b04ae3b4d846c9abc46bab87f86bfb9cf4"
> > +PV = "4.3.1+git${SRCPV}"
> >...
>
> These are the actual releases, PV should not say +git${SRCPV}
> for them.
>
> Not a bug you introduced, but can be fixed now.
>
> cu
> Adrian
>
> --
>
>"Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
>"Only a promise," Lao Er said.
>Pearl S. Buck - Dragon Seed
>
>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] Git commit process question.
Just to make clear, the AUH workflow does require the maintainer to sign off and edit a commit message via 'git commit -s --reset-author --amend' for every commit, so AUH does not get in the way of useful commit messages. Alex On Wed, 3 Apr 2019 at 12:31, Burton, Ross wrote: > > On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote: > > > The kernel does not have "upgrade foo to the latest upstream version" > > > commits. > > > > > > With the Automatic Upgrade Helper this is a semi-automatic task, and > > > most of the time there is no specific motivation other than upgrading > > > to the latest upstream version. > > > > But since that's just filling in a template the body can also be a > > template perhaps with useful AUH data (run at ... by ... ?) ? > > Apart from making the commit message longer what does this achieve? > The commit already has a timestamp and author. > > Ross > -- > ___ > Openembedded-core mailing list > openembedded-c...@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] Git commit process question.
On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote: > > The kernel does not have "upgrade foo to the latest upstream version" > > commits. > > > > With the Automatic Upgrade Helper this is a semi-automatic task, and > > most of the time there is no specific motivation other than upgrading > > to the latest upstream version. > > But since that's just filling in a template the body can also be a > template perhaps with useful AUH data (run at ... by ... ?) ? Apart from making the commit message longer what does this achieve? The commit already has a timestamp and author. Ross -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-initramfs][PATCH] dracut: fix udevdir not found
In commit [9d1b81c dracut.sh: improve udevdir and systemdutildir fallback logic], it checked a common binary `collect' to localte udevdir. While upgrading systemd to 241, it dropped binary `collect'. [https://github.com/systemd/systemd/commit/a168792c2d95695fd30c0371d4b3890a9df1eafb] So check binary `ata_id' to instead. Signed-off-by: Hongxu Jia --- .../dracut/0001-dracut.sh-improve-udevdir.patch| 39 ++ .../recipes-devtools/dracut/dracut_git.bb | 1 + 2 files changed, 40 insertions(+) create mode 100644 meta-initramfs/recipes-devtools/dracut/dracut/0001-dracut.sh-improve-udevdir.patch diff --git a/meta-initramfs/recipes-devtools/dracut/dracut/0001-dracut.sh-improve-udevdir.patch b/meta-initramfs/recipes-devtools/dracut/dracut/0001-dracut.sh-improve-udevdir.patch new file mode 100644 index 000..06e0a09 --- /dev/null +++ b/meta-initramfs/recipes-devtools/dracut/dracut/0001-dracut.sh-improve-udevdir.patch @@ -0,0 +1,39 @@ +From 974f728410052bc8fa18d93dc0c1a991bcdb96e6 Mon Sep 17 00:00:00 2001 +From: Hongxu Jia +Date: Wed, 3 Apr 2019 15:24:47 +0800 +Subject: [PATCH] dracut.sh: improve udevdir + +In commit [9d1b81c dracut.sh: improve udevdir and systemdutildir +fallback logic], it checked a common binary `collect' to localte +udevdir. + +But upstream systemd drop binary `collect'. +[https://github.com/systemd/systemd/commit/a168792c2d95695fd30c0371d4b3890a9df1eafb] + +So check binary `ata_id' to instead. + +Upstream-Status: Submitted [https://github.com/dracutdevs/dracut/pull/558] + +Signed-off-by: Hongxu Jia +--- + dracut.sh | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/dracut.sh b/dracut.sh +index 3dc2adc..cc8b01a 100755 +--- a/dracut.sh b/dracut.sh +@@ -1311,8 +1311,8 @@ done + [[ -d $udevdir ]] \ + || udevdir="$(pkg-config udev --variable=udevdir 2>/dev/null)" + if ! [[ -d "$udevdir" ]]; then +-[[ -e /lib/udev/collect ]] && udevdir=/lib/udev +-[[ -e /usr/lib/udev/collect ]] && udevdir=/usr/lib/udev ++[[ -e /lib/udev/ata_id ]] && udevdir=/lib/udev ++[[ -e /usr/lib/udev/ata_id ]] && udevdir=/usr/lib/udev + fi + + [[ -d $systemdutildir ]] \ +-- +2.7.4 + diff --git a/meta-initramfs/recipes-devtools/dracut/dracut_git.bb b/meta-initramfs/recipes-devtools/dracut/dracut_git.bb index dd2e8bb..344dfec 100644 --- a/meta-initramfs/recipes-devtools/dracut/dracut_git.bb +++ b/meta-initramfs/recipes-devtools/dracut/dracut_git.bb @@ -12,6 +12,7 @@ PV = "049" SRCREV = "225e4b94cbdb702cf512490dcd2ad9ca5f5b22c1" SRC_URI = "git://git.kernel.org/pub/scm/boot/dracut/dracut.git;protocol=http \ file://0001-util.h-include-sys-reg.h-when-libc-glibc.patch \ + file://0001-dracut.sh-improve-udevdir.patch \ " DEPENDS += "kmod" -- 2.7.4 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] Git commit process question.
On Tue, Apr 02, 2019 at 03:46:14PM -0400, Tom Rini wrote: > On Tue, Apr 02, 2019 at 09:51:21AM +0300, Adrian Bunk wrote: > > On Mon, Apr 01, 2019 at 04:20:41PM -0700, akuster808 wrote: > > > > > > > > > On 4/1/19 4:02 PM, Richard Purdie wrote: > > > > On Mon, 2019-04-01 at 15:33 -0700, akuster808 wrote: > > > >> Hello, > > > >> > > > >> I have noticed a large number of git commits with no header > > > >> information being accepted. > > > > Can you be more specific about what "no header information" means? You > > > > mean a shortlog and no full log message? > > > Commits with just a "subject" and signoff. No additional information > > > > > > We tend to reference back to how the kernel does things. > > > > > > https://www.kernel.org/doc/html/latest/process/submitting-patches.html > > > These two sections in particular. > > > > > > > > > 2) Describe your changes > > > > > > Describe your problem. Whether your patch is a one-line bug fix or 5000 > > > lines of a new feature, there must be an underlying problem that > > > motivated you to do this work. Convince the reviewer that there is a > > > problem worth fixing and that it makes sense for them to read past the > > > first paragraph. > > >... > > > > The kernel does not have "upgrade foo to the latest upstream version" > > commits. > > > > With the Automatic Upgrade Helper this is a semi-automatic task, and > > most of the time there is no specific motivation other than upgrading > > to the latest upstream version. > > But since that's just filling in a template the body can also be a > template perhaps with useful AUH data (run at ... by ... ?) ? That would be more trivial than useful. And so far noone has stated any actual problem that would be solved by adding such a new requirement. > Tom cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-java][PATCH 0/2] Allow building jre from hosttools
Hi Andrej, Peter, On 01/04/2019 16:08, Andrej Valek wrote: From: Peter Marko Buildding whole native openjdk toolchain takes very long time as is a waste of resources. Following layer configuration allows to build from hosttools: HOSTTOOLS += "java javac pack200" ASSUME_PROVIDED += "openjdk-8-native" This requires some changes in the recipes. Thanks for this series. I'll merge it to master-next, take a look at it ASAP and run it through my tests. Unfortunately I'm currently quite busy so please don't expect any results before end of next week. Sorry for that. regards;Richard.L Peter Marko (2): openjre-8: allow build from hosttools openjdk-8: add missing unzip-native dependency recipes-core/openjdk/openjdk-8-cross.inc | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-java][PATCH] layer.conf: Add warrior to compatible release series
Signed-off-by: Richard Leitner
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index b03a608..90236be 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -7,7 +7,7 @@ BBFILES += "${LAYERDIR}/recipes*/*/*.bb
${LAYERDIR}/recipes*/*/*.bbappend"
BBFILE_COLLECTIONS += "meta-java"
BBFILE_PATTERN_meta-java := "^${LAYERDIR}/"
BBFILE_PRIORITY_meta-java = "10"
-LAYERSERIES_COMPAT_meta-java = "thud"
+LAYERSERIES_COMPAT_meta-java = "thud warrior"
LICENSE_PATH += "${LAYERDIR}/licenses"
--
2.20.1
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
On Wed, Apr 03, 2019 at 10:28:42AM +0200, Vincent Prince wrote:
> Signed-off-by: Vincent Prince
> ---
> meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> index 9aff59c..2f99417 100644
> --- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> +++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> @@ -4,8 +4,8 @@ LICENSE = "MIT"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
> DEPENDS = "zeromq"
>
> -SRCREV = "6aa3ab686e916cb0e62df7fa7d12e0b13ae9fae6"
> -PV = "4.2.3+git${SRCPV}"
> +SRCREV = "213da0b04ae3b4d846c9abc46bab87f86bfb9cf4"
> +PV = "4.3.1+git${SRCPV}"
>...
These are the actual releases, PV should not say +git${SRCPV}
for them.
Not a bug you introduced, but can be fixed now.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 3/3] czmq: bump version 4.1.1 => 4.2.0
I forgot to remove 0001-Problem-out-of-date-with-zproject.patch file, it
will fixed in v2.
Le mer. 3 avr. 2019 à 10:29, Vincent Prince a
écrit :
> Also, add curl and systemd to PACKAGECONFIG
>
> Signed-off-by: Vincent Prince
> ---
> .../zeromq/{czmq_4.1.1.bb => czmq_4.2.0.bb}| 18
> +-
> 1 file changed, 9 insertions(+), 9 deletions(-)
> rename meta-oe/recipes-connectivity/zeromq/{czmq_4.1.1.bb =>
> czmq_4.2.0.bb} (56%)
>
> diff --git a/meta-oe/recipes-connectivity/zeromq/czmq_4.1.1.bb
> b/meta-oe/recipes-connectivity/zeromq/czmq_4.2.0.bb
> similarity index 56%
> rename from meta-oe/recipes-connectivity/zeromq/czmq_4.1.1.bb
> rename to meta-oe/recipes-connectivity/zeromq/czmq_4.2.0.bb
> index f2db004..4ec1c04 100644
> --- a/meta-oe/recipes-connectivity/zeromq/czmq_4.1.1.bb
> +++ b/meta-oe/recipes-connectivity/zeromq/czmq_4.2.0.bb
> @@ -1,15 +1,13 @@
> -DESCRIPTION = "C bindings for ZeroMQ"
> -HOMEPAGE = "http://www.zeromq.org;
> +DESCRIPTION = "High-level C binding for 0MQ"
> +HOMEPAGE = "http://czmq.zeromq.org/;
> LICENSE = "MPL-2.0"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=9741c346eef56131163e13b9db1241b3"
> DEPENDS = "zeromq"
>
> -SRC_URI = "
> https://github.com/zeromq/czmq/releases/download/v${PV}/czmq-${PV}.tar.gz
> \
> -file://0001-Problem-out-of-date-with-zproject.patch \
> -"
> +SRC_URI = "
> https://github.com/zeromq/czmq/releases/download/v${PV}/czmq-${PV}.tar.gz;
>
> -SRC_URI[md5sum] = "6d3a6fdd25c2bb29897c53670dce97bf"
> -SRC_URI[sha256sum] =
> "f00ff419881dc2a05d0686c8467cd89b4882677fc56f31c0e2cc81c134cbb0c0"
> +SRC_URI[md5sum] = "7e09997db6ac3b25e8ed104053040722"
> +SRC_URI[sha256sum] =
> "cfab29c2b3cc8a845749758a51e1dd5f5160c1ef57e2a41ea96e4c2dcc8feceb"
>
> inherit cmake
>
> @@ -17,14 +15,16 @@ PACKAGES = "lib${BPN} lib${BPN}-dev
> lib${BPN}-staticdev ${PN} ${PN}-dbg"
>
> FILES_${PN} = "${bindir}/*"
> FILES_lib${BPN} = "${libdir}/*.so.*"
> -FILES_lib${BPN}-dev = "${libdir}/*.so ${libdir}/pkgconfig ${includedir}"
> +FILES_lib${BPN}-dev = "${libdir}/*.so ${libdir}/pkgconfig ${includedir}
> ${datadir}/cmake"
> FILES_lib${BPN}-staticdev = "${libdir}/lib*.a"
>
> RDEPENDS_lib${BPN}-dev = "zeromq-dev"
>
> -PACKAGECONFIG ??= "lz4 uuid"
> +PACKAGECONFIG ??= "lz4 uuid curl ${@bb.utils.filter('DISTRO_FEATURES',
> 'systemd', d)}"
> PACKAGECONFIG[lz4] = ",-DCMAKE_DISABLE_FIND_PACKAGE_lz4=TRUE,lz4"
> PACKAGECONFIG[uuid] = ",-DCMAKE_DISABLE_FIND_PACKAGE_uuid=TRUE,util-linux"
> +PACKAGECONFIG[curl] = ",-DCMAKE_DISABLE_FIND_PACKAGE_libcurl=TRUE,curl"
> +PACKAGECONFIG[systemd] =
> ",-DCMAKE_DISABLE_FIND_PACKAGE_systemd=TRUE,systemd"
>
> BBCLASSEXTEND = "nativesdk"
>
> --
> 2.7.4
>
>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][patch] dnf-plugin-tui: new recipe
Apologies, but i have to say no to this patch.
1) Most people do not want dnf tooling in their SDKs. Your patches
include that unconditionally.
2) bbappends do not belong in meta-oe, as they modify behavior of
original recipes quietly when you enable that layer. You need to
modify the original recipes, and send patches for that.
3) The recipe for the tui plugin should not be nativesdk-specific. If
someone wants that on target, they should be able to.
4) You had previously submitted this to oe-core, it was discussed, and
the outcome was that it's better to add generic tooling support to
eSDK for the use case (customizing a rootfs). Meta-oe is not the right
place for a dnf/rpm-specific solution, especially if it's forced on
everyone.
I would suggest that you make your own layer for this (e.g.
meta-dnf-tui) and publish that in github next to the tui plugin.
Alex
On Wed, 3 Apr 2019 at 07:08, Zheng Ruoqin wrote:
>
> A new recipe for dnf-plugin called tui.
> This plugin can work in nativesdk environment, and provide some additional
> functions:
> 1. Add new command dnf tui --init to make dnf to work on host
> 2. Text-based user interface for dnf.
> 3. Manage SPDX files
> 4. Manage SRPM files
> 5. Add installation samples for dnf
>
> More details, please reference to
> https://github.com/ubinux/dnf-plugin-tui/tree/master.
>
> In addition, modify some nativesdk recipes to include dnf-plugin-tui in
> meta-toolchain.
>
> Signed-off-by: Zheng Ruoqin
> ---
> .../recipes-core/meta/meta-environment.bbappend| 3 +++
> .../nativesdk-packagegroup-sdk-host.bbappend | 2 ++
> .../recipes-devtools/dnf-plugin-tui/dnf_%.bbappend | 29
> ++
> .../dnf-plugin-tui/nativesdk-dnf-plugin-tui.bb | 29
> ++
> 4 files changed, 63 insertions(+)
> create mode 100644 meta-oe/recipes-core/meta/meta-environment.bbappend
> create mode 100644
> meta-oe/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
> create mode 100644 meta-oe/recipes-devtools/dnf-plugin-tui/dnf_%.bbappend
> create mode 100644
> meta-oe/recipes-devtools/dnf-plugin-tui/nativesdk-dnf-plugin-tui.bb
>
> diff --git a/meta-oe/recipes-core/meta/meta-environment.bbappend
> b/meta-oe/recipes-core/meta/meta-environment.bbappend
> new file mode 100644
> index 000..2ac268f
> --- /dev/null
> +++ b/meta-oe/recipes-core/meta/meta-environment.bbappend
> @@ -0,0 +1,3 @@
> +create_sdk_files_append() {
> +echo 'export MACHINE_ARCH=${MACHINE_ARCH}' >> $script
> +}
> diff --git
> a/meta-oe/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
> b/meta-oe/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
> new file mode 100644
> index 000..9f85825
> --- /dev/null
> +++
> b/meta-oe/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
> @@ -0,0 +1,2 @@
> +RDEPENDS_${PN}_append = " nativesdk-dnf-plugin-tui \
> + nativesdk-createrepo-c"
> diff --git a/meta-oe/recipes-devtools/dnf-plugin-tui/dnf_%.bbappend
> b/meta-oe/recipes-devtools/dnf-plugin-tui/dnf_%.bbappend
> new file mode 100644
> index 000..ce683e4
> --- /dev/null
> +++ b/meta-oe/recipes-devtools/dnf-plugin-tui/dnf_%.bbappend
> @@ -0,0 +1,29 @@
> +RDEPENDS_${PN}_class-nativesdk += " \
> + python3-core \
> + python3-codecs \
> + python3-netclient \
> + python3-email \
> + python3-threading \
> + python3-distutils \
> + python3-logging \
> + python3-fcntl \
> + librepo \
> + python3-shell \
> + libcomps \
> + libdnf \
> + python3-sqlite3 \
> + python3-compression \
> + python3-rpm \
> + python3-iniparse \
> + python3-json \
> + python3-curses \
> + python3-misc \
> + python3-gpg \
> + libnewt-python \
> + "
> +
> +do_install_append_class-nativesdk() {
> +create_wrapper ${D}/${bindir}/dnf \
> +RPM_CONFIGDIR=${SDKPATHNATIVE}${libdir_nativesdk}/rpm \
> +RPM_NO_CHROOT_FOR_SCRIPTS=1
> +}
> diff --git
> a/meta-oe/recipes-devtools/dnf-plugin-tui/nativesdk-dnf-plugin-tui.bb
> b/meta-oe/recipes-devtools/dnf-plugin-tui/nativesdk-dnf-plugin-tui.bb
> new file mode 100644
> index 000..4fbbac8
> --- /dev/null
> +++ b/meta-oe/recipes-devtools/dnf-plugin-tui/nativesdk-dnf-plugin-tui.bb
> @@ -0,0 +1,29 @@
> +SUMMARY = "A text-based user interface plugin for dnf, used in toolchian
> environment"
> +LICENSE = "GPLv2"
> +
> +LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> +
> +SRC_URI = "git://github.com/ubinux/dnf-plugin-tui.git;branch=master "
> +
> +SRCREV = "a743116fa78a20f9828533c1de79ad8e4ab2d16c"
> +
> +inherit nativesdk distutils3-base
> +
> +S = "${WORKDIR}/git"
> +
> +RDEPENDS_${PN} += " \
> + nativesdk-dnf \
> + nativesdk-libnewt-python \
> + "
> +
> +do_install_append() {
> +install -d ${D}${datadir}/dnf
> +install -m 0755 ${S}/samples/* ${D}${datadir}/dnf
> +install -d ${D}${PYTHON_SITEPACKAGES_DIR}/dnf-plugins/mkimg
> +install -m
[oe] [meta-oe][PATCH 3/3] czmq: bump version 4.1.1 => 4.2.0
Also, add curl and systemd to PACKAGECONFIG
Signed-off-by: Vincent Prince
---
.../zeromq/{czmq_4.1.1.bb => czmq_4.2.0.bb}| 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
rename meta-oe/recipes-connectivity/zeromq/{czmq_4.1.1.bb => czmq_4.2.0.bb}
(56%)
diff --git a/meta-oe/recipes-connectivity/zeromq/czmq_4.1.1.bb
b/meta-oe/recipes-connectivity/zeromq/czmq_4.2.0.bb
similarity index 56%
rename from meta-oe/recipes-connectivity/zeromq/czmq_4.1.1.bb
rename to meta-oe/recipes-connectivity/zeromq/czmq_4.2.0.bb
index f2db004..4ec1c04 100644
--- a/meta-oe/recipes-connectivity/zeromq/czmq_4.1.1.bb
+++ b/meta-oe/recipes-connectivity/zeromq/czmq_4.2.0.bb
@@ -1,15 +1,13 @@
-DESCRIPTION = "C bindings for ZeroMQ"
-HOMEPAGE = "http://www.zeromq.org;
+DESCRIPTION = "High-level C binding for 0MQ"
+HOMEPAGE = "http://czmq.zeromq.org/;
LICENSE = "MPL-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=9741c346eef56131163e13b9db1241b3"
DEPENDS = "zeromq"
-SRC_URI =
"https://github.com/zeromq/czmq/releases/download/v${PV}/czmq-${PV}.tar.gz \
-file://0001-Problem-out-of-date-with-zproject.patch \
-"
+SRC_URI =
"https://github.com/zeromq/czmq/releases/download/v${PV}/czmq-${PV}.tar.gz;
-SRC_URI[md5sum] = "6d3a6fdd25c2bb29897c53670dce97bf"
-SRC_URI[sha256sum] =
"f00ff419881dc2a05d0686c8467cd89b4882677fc56f31c0e2cc81c134cbb0c0"
+SRC_URI[md5sum] = "7e09997db6ac3b25e8ed104053040722"
+SRC_URI[sha256sum] =
"cfab29c2b3cc8a845749758a51e1dd5f5160c1ef57e2a41ea96e4c2dcc8feceb"
inherit cmake
@@ -17,14 +15,16 @@ PACKAGES = "lib${BPN} lib${BPN}-dev lib${BPN}-staticdev
${PN} ${PN}-dbg"
FILES_${PN} = "${bindir}/*"
FILES_lib${BPN} = "${libdir}/*.so.*"
-FILES_lib${BPN}-dev = "${libdir}/*.so ${libdir}/pkgconfig ${includedir}"
+FILES_lib${BPN}-dev = "${libdir}/*.so ${libdir}/pkgconfig ${includedir}
${datadir}/cmake"
FILES_lib${BPN}-staticdev = "${libdir}/lib*.a"
RDEPENDS_lib${BPN}-dev = "zeromq-dev"
-PACKAGECONFIG ??= "lz4 uuid"
+PACKAGECONFIG ??= "lz4 uuid curl ${@bb.utils.filter('DISTRO_FEATURES',
'systemd', d)}"
PACKAGECONFIG[lz4] = ",-DCMAKE_DISABLE_FIND_PACKAGE_lz4=TRUE,lz4"
PACKAGECONFIG[uuid] = ",-DCMAKE_DISABLE_FIND_PACKAGE_uuid=TRUE,util-linux"
+PACKAGECONFIG[curl] = ",-DCMAKE_DISABLE_FIND_PACKAGE_libcurl=TRUE,curl"
+PACKAGECONFIG[systemd] = ",-DCMAKE_DISABLE_FIND_PACKAGE_systemd=TRUE,systemd"
BBCLASSEXTEND = "nativesdk"
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH 2/3] cppzmq: bump version 4.2.3 => 4.3.1
Signed-off-by: Vincent Prince
---
meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
index 9aff59c..2f99417 100644
--- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
+++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
@@ -4,8 +4,8 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
DEPENDS = "zeromq"
-SRCREV = "6aa3ab686e916cb0e62df7fa7d12e0b13ae9fae6"
-PV = "4.2.3+git${SRCPV}"
+SRCREV = "213da0b04ae3b4d846c9abc46bab87f86bfb9cf4"
+PV = "4.3.1+git${SRCPV}"
SRC_URI = "git://github.com/zeromq/cppzmq.git"
@@ -13,6 +13,8 @@ S = "${WORKDIR}/git"
inherit cmake
+EXTRA_OECMAKE = "-DCPPZMQ_BUILD_TESTS=OFF"
+
PACKAGES = "${PN}-dev"
RDEPENDS_${PN}-dev = "zeromq-dev"
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH 1/3] zeromq: bump version 4.2.5 => 4.3.1
Also, use cmake instead of autotools to build it.
Signed-off-by: Vincent Prince
---
.../recipes-connectivity/zeromq/zeromq_4.2.5.bb| 32 --
.../recipes-connectivity/zeromq/zeromq_4.3.1.bb| 26 ++
2 files changed, 26 insertions(+), 32 deletions(-)
delete mode 100644 meta-oe/recipes-connectivity/zeromq/zeromq_4.2.5.bb
create mode 100644 meta-oe/recipes-connectivity/zeromq/zeromq_4.3.1.bb
diff --git a/meta-oe/recipes-connectivity/zeromq/zeromq_4.2.5.bb
b/meta-oe/recipes-connectivity/zeromq/zeromq_4.2.5.bb
deleted file mode 100644
index 356348b..000
--- a/meta-oe/recipes-connectivity/zeromq/zeromq_4.2.5.bb
+++ /dev/null
@@ -1,32 +0,0 @@
-DESCRIPTION = "ZeroMQ looks like an embeddable networking library but acts
like a concurrency framework"
-HOMEPAGE = "http://www.zeromq.org;
-LICENSE = "LGPLv3+"
-LIC_FILES_CHKSUM = "file://COPYING.LESSER;md5=d5311495d952062e0e4fbba39cbf3de1"
-
-PACKAGECONFIG ??= "libsodium"
-PACKAGECONFIG[libsodium] = "--with-libsodium, --without-libsodium, libsodium"
-
-SRC_URI =
"http://github.com/zeromq/libzmq/releases/download/v${PV}/zeromq-${PV}.tar.gz \
-file://run-ptest \
-"
-SRC_URI[md5sum] = "a1c95b34384257e986842f4d006957b8"
-SRC_URI[sha256sum] =
"cc9090ba35713d59bb2f7d7965f877036c49c5558ea0c290b0dcc6f2a17e489f"
-
-S = "${WORKDIR}/zeromq-${PV}"
-
-#Uncomment to choose polling system manually. valid values are kqueue, epoll,
devpoll, poll or select
-#EXTRA_OECONF += "--with-poller=kqueue"
-#CFLAGS_append = " -O0"
-#CXXFLAGS_append = " -O0"
-
-inherit autotools ptest pkgconfig
-
-do_compile_ptest () {
-echo 'buildtest-TESTS: $(check_PROGRAMS)' >> ${B}/Makefile
-oe_runmake buildtest-TESTS
-}
-
-do_install_ptest () {
-install -d ${D}${PTEST_PATH}/tests
-install -m 0755 ${B}/tests/.libs/test_* ${D}${PTEST_PATH}/tests
-}
diff --git a/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.1.bb
b/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.1.bb
new file mode 100644
index 000..6e13376
--- /dev/null
+++ b/meta-oe/recipes-connectivity/zeromq/zeromq_4.3.1.bb
@@ -0,0 +1,26 @@
+DESCRIPTION = "ZeroMQ looks like an embeddable networking library but acts
like a concurrency framework"
+HOMEPAGE = "http://www.zeromq.org;
+LICENSE = "LGPLv3+"
+LIC_FILES_CHKSUM = "file://COPYING.LESSER;md5=d5311495d952062e0e4fbba39cbf3de1"
+
+PACKAGECONFIG ??= "libsodium"
+PACKAGECONFIG[libsodium] = "-DWITH_LIBSODIUM=ON,-DWITH_LIBSODIUM=OFF,
libsodium"
+
+SRC_URI =
"http://github.com/zeromq/libzmq/releases/download/v${PV}/zeromq-${PV}.tar.gz \
+file://run-ptest \
+"
+SRC_URI[md5sum] = "64cbf3577afdbfda30358bc757a6ac83"
+SRC_URI[sha256sum] =
"bcbabe1e2c7d0eec4ed612e10b94b112dd5f06fcefa994a0c79a45d835cd21eb"
+
+inherit cmake ptest pkgconfig
+
+EXTRA_OECMAKE = "${@bb.utils.contains('PTEST_ENABLED', '1',
'-DBUILD_TESTS=ON', '-DBUILD_TESTS=OFF', d)} \
+ -DCMAKE_SKIP_RPATH=ON \
+"
+
+do_install_ptest () {
+install -d ${D}${PTEST_PATH}/tests
+install -m 0755 ${B}/bin/test_* ${D}${PTEST_PATH}/tests
+}
+
+FILES_${PN}-doc += "${datadir}/zmq/*.txt"
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
