Re: [oe] [meta-networking][PATCH] Install a systemd unit into ${systemd_unitdir} only with systemd in DISTRO_FEATURES
Please apply the patch . -Original Message- From: Guo Chunrong-B40290 Sent: Friday, July 05, 2013 1:29 PM To: openembedded-devel@lists.openembedded.org Cc: Liu Ting-B28495; Luo Zhenhua-B19537; Guo Chunrong-B40290; Yu Zongchun-B40527; Guo Chunrong-B40290 Subject: [meta-networking][PATCH] Install a systemd unit into ${systemd_unitdir} only with systemd in DISTRO_FEATURES Signed-off-by: Chunrong Guo b40...@freescale.com --- .../recipes-protocols/net-snmp/net-snmp_5.7.2.bb | 11 +++ .../recipes-support/dnsmasq/dnsmasq.inc|5 - .../recipes-support/nis/yp-tools_2.12.bb |8 +--- .../recipes-support/nis/ypbind-mt_1.36.bb |8 +--- meta-networking/recipes-support/ntp/ntp.inc| 12 +++- 5 files changed, 28 insertions(+), 16 deletions(-) diff --git a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb index d21995a..2eece50 100644 --- a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb +++ b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb @@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = file://README;beginline=3;endline=8;md5=7f7f00ba639ac8e8deb5 DEPENDS = openssl libnl pciutils -PR = r1 +PR = r2 SRC_URI = ${SOURCEFORGE_MIRROR}/net-snmp/net-snmp-${PV}.tar.gz \ file://init \ @@ -51,9 +51,12 @@ do_install_append() { -e s@^includedir=.*@includedir=${STAGING_INCDIR}@g \ -e s@^libdir=.*@libdir=${STAGING_LIBDIR}@g \ -i ${STAGING_BINDIR}/net-snmp-config -install -d ${D}${systemd_unitdir}/system -install -m 0644 ${WORKDIR}/snmpd.service ${D}${systemd_unitdir}/system -install -m 0644 ${WORKDIR}/snmptrapd.service ${D}${systemd_unitdir}/system + +if ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)}; then +install -d ${D}${systemd_unitdir}/system +install -m 0644 ${WORKDIR}/snmpd.service ${D}${systemd_unitdir}/system +install -m 0644 ${WORKDIR}/snmptrapd.service ${D}${systemd_unitdir}/system +fi } PACKAGES = ${PN}-dbg ${PN}-doc ${PN}-dev ${PN}-staticdev ${PN}-static ${PN}-libs \ diff --git a/meta-networking/recipes-support/dnsmasq/dnsmasq.inc b/meta-networking/recipes-support/dnsmasq/dnsmasq.inc index 0f5b273..242f143 100644 --- a/meta-networking/recipes-support/dnsmasq/dnsmasq.inc +++ b/meta-networking/recipes-support/dnsmasq/dnsmasq.inc @@ -31,9 +31,11 @@ do_install () { install -m 644 ${WORKDIR}/dnsmasq.conf ${D}${sysconfdir}/ install -m 755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/dnsmasq +if ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)}; + then install -d ${D}${systemd_unitdir}/system install -m 0644 ${WORKDIR}/dnsmasq.service ${D}${systemd_unitdir}/system - +fi + if [ ${@base_contains('PACKAGECONFIG', 'dbus', 'dbus', '', d)} != ]; then install -d ${D}${sysconfdir}/dbus-1/system.d install -m 644 dbus/dnsmasq.conf ${D}${sysconfdir}/dbus-1/system.d/ @@ -46,3 +48,4 @@ RPROVIDES_${PN} += ${PN}-systemd RREPLACES_${PN} += ${PN}-systemd RCONFLICTS_${PN} += ${PN}-systemd SYSTEMD_SERVICE_${PN} = dnsmasq.service + diff --git a/meta-networking/recipes-support/nis/yp-tools_2.12.bb b/meta-networking/recipes-support/nis/yp-tools_2.12.bb index 0017845..65c4429 100644 --- a/meta-networking/recipes-support/nis/yp-tools_2.12.bb +++ b/meta-networking/recipes-support/nis/yp-tools_2.12.bb @@ -1,7 +1,7 @@ # This package builds tools to manage NIS # The source package is utils/net/NIS/yp-tools # -PR = r3 +PR = r4 DESCRIPTION=\ Network Information Service tools. \ This package contains ypcat, ypmatch, ypset, \ @@ -26,6 +26,8 @@ RCONFLICTS_${PN} += ${PN}-systemd SYSTEMD_SERVICE_${PN} = domainname.service do_install_append() { -install -d ${D}${systemd_unitdir}/system -install -m 0644 ${WORKDIR}/domainname.service ${D}${systemd_unitdir}/system +if ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)}; then +install -d ${D}${systemd_unitdir}/system +install -m 0644 ${WORKDIR}/domainname.service ${D}${systemd_unitdir}/system +fi } diff --git a/meta-networking/recipes-support/nis/ypbind-mt_1.36.bb b/meta-networking/recipes-support/nis/ypbind-mt_1.36.bb index 35ef16a..85ecaf8 100644 --- a/meta-networking/recipes-support/nis/ypbind-mt_1.36.bb +++ b/meta-networking/recipes-support/nis/ypbind-mt_1.36.bb @@ -1,7 +1,7 @@ # This package builds the NIS ypbind daemon # The source package is utils/net/NIS/ypbind-mt # -PR = r3 +PR = r4 DESCRIPTION=\ Multithreaded NIS bind service (ypbind-mt). \ ypbind-mt is a complete new implementation of a NIS \ @@ -40,8 +40,10 @@ do_install_append () { # TODO, use update-rc.d ln -s ../init.d/ypbind ${D}${sysconfdir}/rcS.d/S44ypbind -install -d ${D}${systemd_unitdir}/system -install -m 0644 ${WORKDIR}/ypbind.service ${D}${systemd_unitdir}/system +if
Re: [oe] [meta-networking][PATCH] Install a systemd unit into ${systemd_unitdir} only with systemd in DISTRO_FEATURES
On Tue, Jul 23, 2013 at 06:34:11AM +, Guo Chunrong-B40290 wrote: Please apply the patch . There is patch for systemd.bbclass on oe-core ML which should resolve this for all recipes with systemd service files: http://lists.openembedded.org/pipermail/openembedded-core/2013-July/081547.html I would prefer to wait until it's resolved in oe-core. -Original Message- From: Guo Chunrong-B40290 Sent: Friday, July 05, 2013 1:29 PM To: openembedded-devel@lists.openembedded.org Cc: Liu Ting-B28495; Luo Zhenhua-B19537; Guo Chunrong-B40290; Yu Zongchun-B40527; Guo Chunrong-B40290 Subject: [meta-networking][PATCH] Install a systemd unit into ${systemd_unitdir} only with systemd in DISTRO_FEATURES Signed-off-by: Chunrong Guo b40...@freescale.com --- .../recipes-protocols/net-snmp/net-snmp_5.7.2.bb | 11 +++ .../recipes-support/dnsmasq/dnsmasq.inc|5 - .../recipes-support/nis/yp-tools_2.12.bb |8 +--- .../recipes-support/nis/ypbind-mt_1.36.bb |8 +--- meta-networking/recipes-support/ntp/ntp.inc| 12 +++- 5 files changed, 28 insertions(+), 16 deletions(-) diff --git a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb index d21995a..2eece50 100644 --- a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb +++ b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb @@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = file://README;beginline=3;endline=8;md5=7f7f00ba639ac8e8deb5 DEPENDS = openssl libnl pciutils -PR = r1 +PR = r2 SRC_URI = ${SOURCEFORGE_MIRROR}/net-snmp/net-snmp-${PV}.tar.gz \ file://init \ @@ -51,9 +51,12 @@ do_install_append() { -e s@^includedir=.*@includedir=${STAGING_INCDIR}@g \ -e s@^libdir=.*@libdir=${STAGING_LIBDIR}@g \ -i ${STAGING_BINDIR}/net-snmp-config -install -d ${D}${systemd_unitdir}/system -install -m 0644 ${WORKDIR}/snmpd.service ${D}${systemd_unitdir}/system -install -m 0644 ${WORKDIR}/snmptrapd.service ${D}${systemd_unitdir}/system + +if ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)}; then +install -d ${D}${systemd_unitdir}/system +install -m 0644 ${WORKDIR}/snmpd.service ${D}${systemd_unitdir}/system +install -m 0644 ${WORKDIR}/snmptrapd.service ${D}${systemd_unitdir}/system +fi } PACKAGES = ${PN}-dbg ${PN}-doc ${PN}-dev ${PN}-staticdev ${PN}-static ${PN}-libs \ diff --git a/meta-networking/recipes-support/dnsmasq/dnsmasq.inc b/meta-networking/recipes-support/dnsmasq/dnsmasq.inc index 0f5b273..242f143 100644 --- a/meta-networking/recipes-support/dnsmasq/dnsmasq.inc +++ b/meta-networking/recipes-support/dnsmasq/dnsmasq.inc @@ -31,9 +31,11 @@ do_install () { install -m 644 ${WORKDIR}/dnsmasq.conf ${D}${sysconfdir}/ install -m 755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/dnsmasq +if ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)}; + then install -d ${D}${systemd_unitdir}/system install -m 0644 ${WORKDIR}/dnsmasq.service ${D}${systemd_unitdir}/system - +fi + if [ ${@base_contains('PACKAGECONFIG', 'dbus', 'dbus', '', d)} != ]; then install -d ${D}${sysconfdir}/dbus-1/system.d install -m 644 dbus/dnsmasq.conf ${D}${sysconfdir}/dbus-1/system.d/ @@ -46,3 +48,4 @@ RPROVIDES_${PN} += ${PN}-systemd RREPLACES_${PN} += ${PN}-systemd RCONFLICTS_${PN} += ${PN}-systemd SYSTEMD_SERVICE_${PN} = dnsmasq.service + diff --git a/meta-networking/recipes-support/nis/yp-tools_2.12.bb b/meta-networking/recipes-support/nis/yp-tools_2.12.bb index 0017845..65c4429 100644 --- a/meta-networking/recipes-support/nis/yp-tools_2.12.bb +++ b/meta-networking/recipes-support/nis/yp-tools_2.12.bb @@ -1,7 +1,7 @@ # This package builds tools to manage NIS # The source package is utils/net/NIS/yp-tools # -PR = r3 +PR = r4 DESCRIPTION=\ Network Information Service tools. \ This package contains ypcat, ypmatch, ypset, \ @@ -26,6 +26,8 @@ RCONFLICTS_${PN} += ${PN}-systemd SYSTEMD_SERVICE_${PN} = domainname.service do_install_append() { -install -d ${D}${systemd_unitdir}/system -install -m 0644 ${WORKDIR}/domainname.service ${D}${systemd_unitdir}/system +if ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)}; then +install -d ${D}${systemd_unitdir}/system +install -m 0644 ${WORKDIR}/domainname.service ${D}${systemd_unitdir}/system +fi } diff --git a/meta-networking/recipes-support/nis/ypbind-mt_1.36.bb b/meta-networking/recipes-support/nis/ypbind-mt_1.36.bb index 35ef16a..85ecaf8 100644 --- a/meta-networking/recipes-support/nis/ypbind-mt_1.36.bb +++ b/meta-networking/recipes-support/nis/ypbind-mt_1.36.bb @@ -1,7 +1,7 @@ # This package builds the NIS ypbind daemon # The source package is
Re: [oe] [meta-oe PATCH] busybox: Follow OE-Core update to 1.12.1 version
On Monday 08 July 2013 13:35:21 Paul Eggleton wrote: On Friday 05 July 2013 19:45:25 Eric Bénard wrote: Le Fri, 05 Jul 2013 18:29:04 +0100, Paul Eggleton paul.eggle...@linux.intel.com a écrit : Could someone *please* figure out what this bbappend is needed for and get it into OE-Core if it is still needed so we can drop it here? it's only here to install /etc/default/busybox-syslog which contains only one line : OPTIONS=-C64 which sets the size of the logbuffer. So obviously this could go into OE-Core. Yes but why is this needed? If we are to merge this into OE-Core we'll need to say why this change is needed in the commit message. ping... Cheers, 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-networking][PATCH] Install a systemd unit into ${systemd_unitdir} only with systemd in DISTRO_FEATURES
[Re: [oe] [meta-networking][PATCH] Install a systemd unit into ${systemd_unitdir} only with systemd in DISTRO_FEATURES] On 13.07.23 (Tue 11:33) Martin Jansa wrote: On Tue, Jul 23, 2013 at 06:34:11AM +, Guo Chunrong-B40290 wrote: Please apply the patch . There is patch for systemd.bbclass on oe-core ML which should resolve this for all recipes with systemd service files: http://lists.openembedded.org/pipermail/openembedded-core/2013-July/081547.html I would prefer to wait until it's resolved in oe-core. As would I. Sorry about that, I should've followed up with you guys last week. I'd started working on basically the same thing, though I was implementing it in slightly a different way. With the current patch under discussion, I think the right thing to do is to instead remove the workarounds in the other recipes I mentioned that already have them once it has been merged. -J. -Original Message- From: Guo Chunrong-B40290 Sent: Friday, July 05, 2013 1:29 PM To: openembedded-devel@lists.openembedded.org Cc: Liu Ting-B28495; Luo Zhenhua-B19537; Guo Chunrong-B40290; Yu Zongchun-B40527; Guo Chunrong-B40290 Subject: [meta-networking][PATCH] Install a systemd unit into ${systemd_unitdir} only with systemd in DISTRO_FEATURES Signed-off-by: Chunrong Guo b40...@freescale.com --- .../recipes-protocols/net-snmp/net-snmp_5.7.2.bb | 11 +++ .../recipes-support/dnsmasq/dnsmasq.inc|5 - .../recipes-support/nis/yp-tools_2.12.bb |8 +--- .../recipes-support/nis/ypbind-mt_1.36.bb |8 +--- meta-networking/recipes-support/ntp/ntp.inc| 12 +++- 5 files changed, 28 insertions(+), 16 deletions(-) diff --git a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb index d21995a..2eece50 100644 --- a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb +++ b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb @@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = file://README;beginline=3;endline=8;md5=7f7f00ba639ac8e8deb5 DEPENDS = openssl libnl pciutils -PR = r1 +PR = r2 SRC_URI = ${SOURCEFORGE_MIRROR}/net-snmp/net-snmp-${PV}.tar.gz \ file://init \ @@ -51,9 +51,12 @@ do_install_append() { -e s@^includedir=.*@includedir=${STAGING_INCDIR}@g \ -e s@^libdir=.*@libdir=${STAGING_LIBDIR}@g \ -i ${STAGING_BINDIR}/net-snmp-config -install -d ${D}${systemd_unitdir}/system -install -m 0644 ${WORKDIR}/snmpd.service ${D}${systemd_unitdir}/system -install -m 0644 ${WORKDIR}/snmptrapd.service ${D}${systemd_unitdir}/system + +if ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)}; then +install -d ${D}${systemd_unitdir}/system +install -m 0644 ${WORKDIR}/snmpd.service ${D}${systemd_unitdir}/system +install -m 0644 ${WORKDIR}/snmptrapd.service ${D}${systemd_unitdir}/system +fi } PACKAGES = ${PN}-dbg ${PN}-doc ${PN}-dev ${PN}-staticdev ${PN}-static ${PN}-libs \ diff --git a/meta-networking/recipes-support/dnsmasq/dnsmasq.inc b/meta-networking/recipes-support/dnsmasq/dnsmasq.inc index 0f5b273..242f143 100644 --- a/meta-networking/recipes-support/dnsmasq/dnsmasq.inc +++ b/meta-networking/recipes-support/dnsmasq/dnsmasq.inc @@ -31,9 +31,11 @@ do_install () { install -m 644 ${WORKDIR}/dnsmasq.conf ${D}${sysconfdir}/ install -m 755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/dnsmasq +if ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)}; + then install -d ${D}${systemd_unitdir}/system install -m 0644 ${WORKDIR}/dnsmasq.service ${D}${systemd_unitdir}/system - +fi + if [ ${@base_contains('PACKAGECONFIG', 'dbus', 'dbus', '', d)} != ]; then install -d ${D}${sysconfdir}/dbus-1/system.d install -m 644 dbus/dnsmasq.conf ${D}${sysconfdir}/dbus-1/system.d/ @@ -46,3 +48,4 @@ RPROVIDES_${PN} += ${PN}-systemd RREPLACES_${PN} += ${PN}-systemd RCONFLICTS_${PN} += ${PN}-systemd SYSTEMD_SERVICE_${PN} = dnsmasq.service + diff --git a/meta-networking/recipes-support/nis/yp-tools_2.12.bb b/meta-networking/recipes-support/nis/yp-tools_2.12.bb index 0017845..65c4429 100644 --- a/meta-networking/recipes-support/nis/yp-tools_2.12.bb +++ b/meta-networking/recipes-support/nis/yp-tools_2.12.bb @@ -1,7 +1,7 @@ # This package builds tools to manage NIS # The source package is utils/net/NIS/yp-tools # -PR = r3 +PR = r4 DESCRIPTION=\ Network Information Service tools. \ This package contains ypcat, ypmatch, ypset, \ @@ -26,6 +26,8 @@ RCONFLICTS_${PN} += ${PN}-systemd SYSTEMD_SERVICE_${PN} = domainname.service do_install_append() { -install -d ${D}${systemd_unitdir}/system -install -m 0644
Re: [oe] [meta-oe PATCH] busybox: Follow OE-Core update to 1.12.1 version
On Tue, Jul 23, 2013 at 6:44 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Monday 08 July 2013 13:35:21 Paul Eggleton wrote: On Friday 05 July 2013 19:45:25 Eric Bénard wrote: Le Fri, 05 Jul 2013 18:29:04 +0100, Paul Eggleton paul.eggle...@linux.intel.com a écrit : Could someone *please* figure out what this bbappend is needed for and get it into OE-Core if it is still needed so we can drop it here? it's only here to install /etc/default/busybox-syslog which contains only one line : OPTIONS=-C64 which sets the size of the logbuffer. So obviously this could go into OE-Core. Yes but why is this needed? If we are to merge this into OE-Core we'll need to say why this change is needed in the commit message. ping... I am working in something else so I cannot work on busybox now. Feel free to handle this. The syslog support would be good to be kept. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://projetos.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe PATCH] busybox: Follow OE-Core update to 1.12.1 version
On Tuesday 23 July 2013 09:09:37 Otavio Salvador wrote: On Tue, Jul 23, 2013 at 6:44 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Monday 08 July 2013 13:35:21 Paul Eggleton wrote: On Friday 05 July 2013 19:45:25 Eric Bénard wrote: Le Fri, 05 Jul 2013 18:29:04 +0100, Paul Eggleton paul.eggle...@linux.intel.com a écrit : Could someone *please* figure out what this bbappend is needed for and get it into OE-Core if it is still needed so we can drop it here? it's only here to install /etc/default/busybox-syslog which contains only one line : OPTIONS=-C64 which sets the size of the logbuffer. So obviously this could go into OE-Core. Yes but why is this needed? If we are to merge this into OE-Core we'll need to say why this change is needed in the commit message. ping... I am working in something else so I cannot work on busybox now. Feel free to handle this. The syslog support would be good to be kept. The problem is it's not clear to me what we should do here. Surely having this bbappend or not isn't the determining factor in whether we have syslog support with systemd...? Cheers, 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] busybox: Follow OE-Core update to 1.12.1 version
On Tue, Jul 23, 2013 at 9:41 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Tuesday 23 July 2013 09:09:37 Otavio Salvador wrote: On Tue, Jul 23, 2013 at 6:44 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Monday 08 July 2013 13:35:21 Paul Eggleton wrote: On Friday 05 July 2013 19:45:25 Eric Bénard wrote: Le Fri, 05 Jul 2013 18:29:04 +0100, Paul Eggleton paul.eggle...@linux.intel.com a écrit : Could someone *please* figure out what this bbappend is needed for and get it into OE-Core if it is still needed so we can drop it here? it's only here to install /etc/default/busybox-syslog which contains only one line : OPTIONS=-C64 which sets the size of the logbuffer. So obviously this could go into OE-Core. Yes but why is this needed? If we are to merge this into OE-Core we'll need to say why this change is needed in the commit message. ping... I am working in something else so I cannot work on busybox now. Feel free to handle this. The syslog support would be good to be kept. The problem is it's not clear to me what we should do here. Surely having this bbappend or not isn't the determining factor in whether we have syslog support with systemd...? With systemd we shouldn't provide it but for sysv we should provide it. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://projetos.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe PATCH] busybox: Follow OE-Core update to 1.12.1 version
On Tuesday 23 July 2013 09:46:36 Otavio Salvador wrote: On Tue, Jul 23, 2013 at 9:41 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Tuesday 23 July 2013 09:09:37 Otavio Salvador wrote: On Tue, Jul 23, 2013 at 6:44 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Monday 08 July 2013 13:35:21 Paul Eggleton wrote: On Friday 05 July 2013 19:45:25 Eric Bénard wrote: Le Fri, 05 Jul 2013 18:29:04 +0100, Paul Eggleton paul.eggle...@linux.intel.com a écrit : Could someone *please* figure out what this bbappend is needed for and get it into OE-Core if it is still needed so we can drop it here? it's only here to install /etc/default/busybox-syslog which contains only one line : OPTIONS=-C64 which sets the size of the logbuffer. So obviously this could go into OE-Core. Yes but why is this needed? If we are to merge this into OE-Core we'll need to say why this change is needed in the commit message. ping... I am working in something else so I cannot work on busybox now. Feel free to handle this. The syslog support would be good to be kept. The problem is it's not clear to me what we should do here. Surely having this bbappend or not isn't the determining factor in whether we have syslog support with systemd...? With systemd we shouldn't provide it but for sysv we should provide it. I still need to know what this is needed for. Surely it doesn't actually enable syslog functionality, just adds one configuration value to it? If that's the case, why is this configuration change needed? Cheers, 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] [meta-networking] Update to standalone tree
If you are only using meta-networking from meta-openembedded, you need read no further. This is only for people using my side-project on github. Absolutely nothing has changed in the official meta-networking. For anyone using the standalone meta-networking subtree I maintain on github, please be aware that I've made a change to the way I create the subtree which, unfortunately, will result in a forced update for all of your branches. And probably a merge on whatever branch you happen to be on already (eg. master). If you get into that scenario, I suggest pushing your current branch with the merge in it off a cliff and re-creating the current branch tracking the up-stream. If you're not in the habit of doing a git-pull, though, this will probably be cleaner: % git fetch --all --tags ; git rebase origin/up-stream-branch-name The reason for this (and the advantage) has been in response to requests I've had to preserve the original (that is, meta-oe) commit hash so it is easy to connect a commit in the standalone meta-networking with the official meta-networking I maintain as a part of the larger meta-oe. The change is small and hopefully self-explanatory, but I won't let that stop me. Before: commit a0f9363caddbfb92212b4bf5d4a2590c451b7cef Author: Roy.Li rongqing...@windriver.com Date: Fri Jul 19 10:19:25 2013 +0800 Upgrade vsftpd to 3.0.0 Upgrade vsftpd to 3.0.0 with below modification: 1. more strict access limitation, like: do not allow anonymous access 2. use vsftpd.ftpusers and vsftpd.user_list to confine user access 3. enable pam if DISTRO_FEATURE includes pam 4. enable tcp-wrapper 5. install vsftpd.conf with 0600 permission, not 0755 Signed-off-by: Roy.Li rongqing...@windriver.com Signed-off-by: Joe MacDonald joe.macdon...@windriver.com After: commit b188e402a04db35424e22cb2b2100b7070648948 Author: Roy.Li rongqing...@windriver.com Date: Fri Jul 19 10:19:25 2013 +0800 Upgrade vsftpd to 3.0.0 (original commit: 441502b68d03a4ce7796436a53c5e95399724ad2) Upgrade vsftpd to 3.0.0 with below modification: 1. more strict access limitation, like: do not allow anonymous access 2. use vsftpd.ftpusers and vsftpd.user_list to confine user access 3. enable pam if DISTRO_FEATURE includes pam 4. enable tcp-wrapper 5. install vsftpd.conf with 0600 permission, not 0755 Signed-off-by: Roy.Li rongqing...@windriver.com Signed-off-by: Joe MacDonald joe.macdon...@windriver.com Where 441502b6... is the commit in meta-oe from Roy that happens to upgrade vsftpd. FWIW, I don't anticipate doing anything destructive like this again. -- -Joe MacDonald. :wq 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-networking] Update to standalone tree
On Tue, Jul 23, 2013 at 01:51:59PM -0400, Joe MacDonald wrote: If you are only using meta-networking from meta-openembedded, you need read no further. This is only for people using my side-project on github. Absolutely nothing has changed in the official meta-networking. Just out of curiosity why do you keep separate tree for it? Is there some diff or is it exactly the same (now also with the same commit IDs?). For anyone using the standalone meta-networking subtree I maintain on github, please be aware that I've made a change to the way I create the subtree which, unfortunately, will result in a forced update for all of your branches. And probably a merge on whatever branch you happen to be on already (eg. master). If you get into that scenario, I suggest pushing your current branch with the merge in it off a cliff and re-creating the current branch tracking the up-stream. If you're not in the habit of doing a git-pull, though, this will probably be cleaner: % git fetch --all --tags ; git rebase origin/up-stream-branch-name The reason for this (and the advantage) has been in response to requests I've had to preserve the original (that is, meta-oe) commit hash so it is easy to connect a commit in the standalone meta-networking with the official meta-networking I maintain as a part of the larger meta-oe. The change is small and hopefully self-explanatory, but I won't let that stop me. Before: commit a0f9363caddbfb92212b4bf5d4a2590c451b7cef Author: Roy.Li rongqing...@windriver.com Date: Fri Jul 19 10:19:25 2013 +0800 Upgrade vsftpd to 3.0.0 Upgrade vsftpd to 3.0.0 with below modification: 1. more strict access limitation, like: do not allow anonymous access 2. use vsftpd.ftpusers and vsftpd.user_list to confine user access 3. enable pam if DISTRO_FEATURE includes pam 4. enable tcp-wrapper 5. install vsftpd.conf with 0600 permission, not 0755 Signed-off-by: Roy.Li rongqing...@windriver.com Signed-off-by: Joe MacDonald joe.macdon...@windriver.com After: commit b188e402a04db35424e22cb2b2100b7070648948 Author: Roy.Li rongqing...@windriver.com Date: Fri Jul 19 10:19:25 2013 +0800 Upgrade vsftpd to 3.0.0 (original commit: 441502b68d03a4ce7796436a53c5e95399724ad2) Upgrade vsftpd to 3.0.0 with below modification: 1. more strict access limitation, like: do not allow anonymous access 2. use vsftpd.ftpusers and vsftpd.user_list to confine user access 3. enable pam if DISTRO_FEATURE includes pam 4. enable tcp-wrapper 5. install vsftpd.conf with 0600 permission, not 0755 Signed-off-by: Roy.Li rongqing...@windriver.com Signed-off-by: Joe MacDonald joe.macdon...@windriver.com Where 441502b6... is the commit in meta-oe from Roy that happens to upgrade vsftpd. FWIW, I don't anticipate doing anything destructive like this again. -- -Joe MacDonald. :wq ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- 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-networking] Update to standalone tree
On Jul 23, 2013, at 10:51 AM, Joe MacDonald joe.macdon...@windriver.com wrote: If you are only using meta-networking from meta-openembedded, you need read no further. This is only for people using my side-project on github. Absolutely nothing has changed in the official meta-networking. For anyone using the standalone meta-networking subtree I maintain on github, whats the advantage of doing so ? you could still checkout the repository and just use meta-networking layer how is above different. We should be careful since in layer universe, this can easily escalate confusion please be aware that I've made a change to the way I create the subtree which, unfortunately, will result in a forced update for all of your branches. And probably a merge on whatever branch you happen to be on already (eg. master). If you get into that scenario, I suggest pushing your current branch with the merge in it off a cliff and re-creating the current branch tracking the up-stream. If you're not in the habit of doing a git-pull, though, this will probably be cleaner: % git fetch --all --tags ; git rebase origin/up-stream-branch-name The reason for this (and the advantage) has been in response to requests I've had to preserve the original (that is, meta-oe) commit hash so it is easy to connect a commit in the standalone meta-networking with the official meta-networking I maintain as a part of the larger meta-oe. The change is small and hopefully self-explanatory, but I won't let that stop me. Before: commit a0f9363caddbfb92212b4bf5d4a2590c451b7cef Author: Roy.Li rongqing...@windriver.com Date: Fri Jul 19 10:19:25 2013 +0800 Upgrade vsftpd to 3.0.0 Upgrade vsftpd to 3.0.0 with below modification: 1. more strict access limitation, like: do not allow anonymous access 2. use vsftpd.ftpusers and vsftpd.user_list to confine user access 3. enable pam if DISTRO_FEATURE includes pam 4. enable tcp-wrapper 5. install vsftpd.conf with 0600 permission, not 0755 Signed-off-by: Roy.Li rongqing...@windriver.com Signed-off-by: Joe MacDonald joe.macdon...@windriver.com After: commit b188e402a04db35424e22cb2b2100b7070648948 Author: Roy.Li rongqing...@windriver.com Date: Fri Jul 19 10:19:25 2013 +0800 Upgrade vsftpd to 3.0.0 (original commit: 441502b68d03a4ce7796436a53c5e95399724ad2) Upgrade vsftpd to 3.0.0 with below modification: 1. more strict access limitation, like: do not allow anonymous access 2. use vsftpd.ftpusers and vsftpd.user_list to confine user access 3. enable pam if DISTRO_FEATURE includes pam 4. enable tcp-wrapper 5. install vsftpd.conf with 0600 permission, not 0755 Signed-off-by: Roy.Li rongqing...@windriver.com Signed-off-by: Joe MacDonald joe.macdon...@windriver.com Where 441502b6... is the commit in meta-oe from Roy that happens to upgrade vsftpd. FWIW, I don't anticipate doing anything destructive like this again. -- -Joe MacDonald. :wq ___ 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] [meta-oe PATCH] busybox: Follow OE-Core update to 1.12.1 version
On 07/23/2013 08:54 PM, Paul Eggleton wrote: On Tuesday 23 July 2013 09:46:36 Otavio Salvador wrote: On Tue, Jul 23, 2013 at 9:41 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Tuesday 23 July 2013 09:09:37 Otavio Salvador wrote: On Tue, Jul 23, 2013 at 6:44 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Monday 08 July 2013 13:35:21 Paul Eggleton wrote: On Friday 05 July 2013 19:45:25 Eric Bénard wrote: Le Fri, 05 Jul 2013 18:29:04 +0100, Paul Eggleton paul.eggle...@linux.intel.com a écrit : Could someone *please* figure out what this bbappend is needed for and get it into OE-Core if it is still needed so we can drop it here? it's only here to install /etc/default/busybox-syslog which contains only one line : OPTIONS=-C64 which sets the size of the logbuffer. So obviously this could go into OE-Core. Yes but why is this needed? If we are to merge this into OE-Core we'll need to say why this change is needed in the commit message. ping... I am working in something else so I cannot work on busybox now. Feel free to handle this. The syslog support would be good to be kept. The problem is it's not clear to me what we should do here. Surely having this bbappend or not isn't the determining factor in whether we have syslog support with systemd...? With systemd we shouldn't provide it but for sysv we should provide it. I still need to know what this is needed for. Surely it doesn't actually enable syslog functionality, just adds one configuration value to it? If that's the case, why is this configuration change needed? Cheers, Paul Hi All, FWIW, there are two bugs which might be related to this. https://bugzilla.yoctoproject.org/show_bug.cgi?id=4837 https://bugzilla.yoctoproject.org/show_bug.cgi?id=4860 My opinion is to respect the same configuration file in both sysv and systemd systems. The configuration file is /etc/syslog-startup.conf. Best Regards, Chen Qi ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-qt5][dylan][RFC PATCH] qt5.inc: Fix qtbase-tools runtime depencency on perl
I'm not sure if it is the right way to do that, but here I go: While building a custom rootfs using poky, meta-oe, meta-ti and meta-qt5 (all on Dylan branch), I got the following error: [...] | Computing transaction...error: Can't install qtbase-tools-5.0.2-r2.0@armv7a_vfp_neon: no package provides /usr/bin/perl [...] qtbase-tools seems to depends and perl (at runtime), but this wasn't specified in any bb file, this patch fixes it. --- recipes-qt/qt5/qt5.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recipes-qt/qt5/qt5.inc b/recipes-qt/qt5/qt5.inc index 87bf5e8..955d5bd 100644 --- a/recipes-qt/qt5/qt5.inc +++ b/recipes-qt/qt5/qt5.inc @@ -22,6 +22,8 @@ OE_QMAKE_PATH_TESTS = ${OE_QMAKE_PATH_QT_TESTS} PACKAGES =. ${PN}-qmlplugins-dbg ${PN}-tools-dbg ${PN}-plugins-dbg ${PN}-qmlplugins ${PN}-tools ${PN}-plugins ${PN}-mkspecs ${PN}-examples-dev ${PN}-examples-staticdev ${PN}-examples-dbg ${PN}-examples +RDEPENDS_${PN}-tools += perl + # extra -dbg packages FILES_${PN}-qmlplugins-dbg = \ ${OE_QMAKE_PATH_QML}/*/.debug \ -- 1.8.1.2 ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel