-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lots of duplicate packages #51
Comments
boa, what a large question.... ----- Original Message -----
ACK, DUP
our iperf 2.0.5 recipe has many patches that upstream doesn't have
ACK, DUP, upstream seems more advance
Buffalo BSP needs this and might need work when we remove them
ACK, DUP
Absolutely NOT. The patches are very version dependent and the CAPWAP hostapd version should not be confused with a normal hostapd.
ACK
ACK
That recipe add new depends: DEPENDS = "pps-tools libevent"
ACK
Or jsut remove it
nothing seems to be using it, so just remove it
Those are install scripts and therefore CAROS or BSP specific.
ACK
Recipes are not current, 18.1 is release and we do also still carry older Erlang version (intentionally).
No, the meta-oe has excessive dependencies (pango, cairo), our version is much leaner.
5.1 is a hard requirement for the old device manager, there is no point in upgrading.
Do we really need nodejs in out tree at all?
Only the old device manager uses it, could be move to meta-scg
ACK
ACK
systemd journal should have replaced that, so could be removed
Buffalo BSP needs this and might need work when we move the firmware-utils
This belongs to the netfilter and nft trees. But the netfilter Also, networking is out main focus, so we need to make sure that
Yes, there are more of that in my tree
see above
ACK
Needed got Buffalo BSP, but might be droppend from master and kept in old version branches
or drop completely (I know some people use it extensively on TPOSS, but IMO this has no place on an appliance).
nothing seems to use it, remove?
is this really needed?
could be, but by creating yet a new layer, we risk duplicating work from meta-oe
ACP
yes.... iproute2 is yet another story
ACK
ACK
drop that crap
ACK
good luck with that -> HINT: don't try
don't think we even use postgresql
Yes, but oe-core might conflict with poky
ACK
Absolutely YES, don't mock with that unless you want to fix erlzmq2
|
duplicating package build recipes from https://github.com/openembedded or http://git.yoctoproject.org permenently increases the maintainance efforts needed on our side. now that we got the subdirs feature in redomat [ https://github.com/carosio/redomat/commit/2ab913d88967214dc84a5f98cfeede902ec88916 ], we could reference stuff instead of duplicating it. local changes can then be bbappended and if the build-recipe upstream is really broken, well, we can suggest to fix it there.
Having reviewed all recipes in caros, I suggest to make this layer depend at least on
oe/meta-openembedded/meta-oe
oe/meta-openembedded/meta-networking
We should consider to also depend on
yoctoproject.org/meta-virtualization
as well as
yoctoproject.org/meta-cloud-services/meta-openstack
Many layers around Yocto also explicetely depend on meta-oe, so that shouldn't be a problem.
oe-core probably conflicts with yocto/poky, but that's not where the big piece of the cake gets eaten anyway.
Please review the package recipes below and let me know if you are fine with some major pruning, I suggest to roll-out 3 phases:
Phase 1: remove outdated versions from meta-caros, use more up-to-date recipes from meta-oe
Phase 2: remove same-version duplicates to use recipes from meta-oe instead
Phase 3: fork meta-oe and update stuff there where ever we got more recent recipes, then pull-request to meta-oe
Objections? Comments?
@RoadRunnr @thz @mgumz
Duplicate recipes:
recipes-benchmark/nuttcp/nuttcp_7.2.1.bb
duplicate of https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-support/nuttcp/nuttcp_7.2.1.bb
recipes-benchmark/iperf/iperf_2.0.4.bb
recipes-benchmark/iperf/iperf_2.0.5.bb
duplicate of https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb
recipes-benchmark/iperf/iperf3_3.0.11.bb
should be upstreamed to https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-benchmark/iperf3/iperf3
recipes-benchmark/netperf/netperf_2.6.0.bb
duplicate of https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-support/netperf/netperf_2.6.0.bb
recipes-bsp/firmware-utils/firmware-utils-native_1.0.bb
should be upstreamed, source should be referenced to svn://svn.openwrt.org/openwrt/trunk/tools/firmware-utils/src instead of copied into meta-caros. See https://github.com/pokymobo/meta-lamobo-r1/blob/master/recipes-support/swconfig/swconfig_1.0-r1.bb for an example of how to properly nick stuff from OpenWrt ;)
recipes-connectivity/tunctl/tunctl_1.5.bb
duplicate of https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-support/tunctl/tunctl_1.5.bb
recipes-connectivity/hostapd/hostapd-capwap-ac_1.1.bb
recipes-connectivity/hostapd/hostapd_1.1.bb
recipes-connectivity/hostapd/hostapd-capwap-wtp_1.1.bb
needs to be examined, maybe this could also work with a bbappend of https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-connectivity/hostapd/hostapd_2.2.bb
recipes-connectivity/iw/iw_3.6.bb
outdated, more recent upstream should be used from
https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-connectivity/iw/iw_3.15.bb
recipes-connectivity/bind/bind_9.9.7-P2.bb
newer version available at
https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-connectivity/bind/bind_9.10.2-P4.bb
recipes-core/ntp/ntp_4.2.6p5.bb
newer version available at
https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-support/ntp/ntp_4.2.8.bb
recipes-core/libmicrohttpd/libmicrohttpd_0.9.39.bb
even more outdated version at
https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-support/libmicrohttpd/libmicrohttpd_0.9.34.bb
should be updated upstream and subsequently de-duplicated.
recipes-core/zsh/zsh_5.0.7.bb
outdated version at
https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-extended/zsh/zsh_5.0.5.bb
should be updated upstream and subsequently de-duplicated.
recipes-core/cunit/cunit_2.1.bb
duplicate of
https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-devtools/cunit/cunit_2.1-3.bb
recipes-core/firstboot/firstboot.bb
???
recipes-core/nginx/nginx_1.7.3.bb
outdated version at
https://github.com/openembedded/meta-openembedded/blob/fido/meta-webserver/recipes-httpd/nginx/nginx_1.4.4.bb
should be updated upstream and subsequently de-duplicated.
ERLANG
what about referencing
https://github.com/joaohf/meta-erlang
recipes-devtools/elixir/elixir_1.1.1.bb
rfc: could this be pushed into meta-erlang?
recipes-devtools/rrdtool/rrdtool_1.4.7.bb
more recent version available at
https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-extended/rrdtool/rrdtool_1.4.8.bb
recipes-devtools/go/golang-cross_1.4.2.bb
maybe https://github.com/errordeveloper/oe-meta-go is what we want?
seems like some people are still depending on go 1.3.x, see
http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/recipes-devtools/go-cross/go-cross-1.3_1.3.bb?id=d0ef47396d1ea7c67b27898f6d0401cbcef45281
recipes-devtools/lua/lua5.1_5.1.5.bb
rfc: any reason to stick with 5.1? if not, we could use
https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-devtools/lua/lua_5.2.2.bb
recipes-devtools/nodejs/nodejs_0.10.25.bb
https://github.com/openwebos/ also duplicates this (outdated) version for some reason. seems like some more dense version-jungle out there
up-to-date upstream:
https://github.com/openembedded/meta-openembedded/blob/master/meta-oe/recipes-devtools/nodejs/nodejs_0.12.7.bb
recipes-extended/perl/libtext-csv-perl_1.32.bb
should we push this into meta-oe?
recipes-extended/lcdproc/lcdproc_0.5.7.bb
slightly outdated recipe
https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-extended/lcdproc/lcdproc_0.5.6.bb
should be updated upstream.
recipes-extended/libconfig/libconfig_1.4.9.bb
duplicate of
https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-extended/libconfig/libconfig_1.4.9.bb
recipes-extended/rsyslog/rsyslog_5.8.0.bb
more up-to-date recipe available at
https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-extended/rsyslog/rsyslog_7.4.4.bb
do we need that old version?
recipes-extended/lzma/lzma-native_4.65.bb
I guess that's needed for some BSP having an outdated bootloader...? (see firmware-utils)
recipes-filter/ulogd/ulogd_2.0.5.bb
submit this to meta-oe/meta-networking ?
recipes-filter/libnetfilter/libnetfilter-cthelper_1.0.0.bb
recipes-filter/libnetfilter/libnetfilter-conntrack_1.0.4.bb
recipes-filter/libnetfilter/libnetfilter-acct_1.0.2.bb
recipes-filter/libnetfilter/libnetfilter-queue_1.0.2.bb
recipes-filter/libnetfilter/libnetfilter-cttimeout_1.0.0.bb
recipes-filter/libnetfilter/libnetfilter-log_1.0.1.bb
shouldn't this be upstreamed towards
https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-filter/libnetfilter/
recipes-filter/conntrack-tools/conntrack-tools_1.4.2.bb
see above
recipes-filter/libnfnetlink/libnfnetlink_1.0.1.bb
see above
recipes-filter/libmnl/libmnl_1.0.3.bb
duplicate of https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-filter/libmnl/libmnl_1.0.3.bb
recipes-filter/ebtables/ebtables_2.0.10-4.bb
duplicate of duplicate of https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-filter/ebtables/ebtables_2.0.10-4.bb
recipes-kernel/linux/linux-caros_3.19.bb
long story, to be discussed seperately...
recipes-mgmt/tmux/tmux_2.0.bb
outdated recipe at https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-extended/tmux/tmux_1.6.bb
should be updated upstream and subsequently de-duplicated.
recipes-networking/ifplugd/ifplugd_0.28.1.bb
push this into meta-oe/meta-networking or keep it here?
recipes-networking/bird/bird_1.5.0.bb
push this into meta-oe/meta-networking or keep it here?
maybe we should create meta-routing similar to https://github.com/openwrt-routing/packages ...?
recipes-networking/libssh2/libssh2_1.4.3.bb
duplicate of https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-support/libssh2/libssh2_1.4.3.bb
recipes-sdn/click/click_git.bb
stay here or live in to-be-create meta-routing ?
recipes-sdn/openvswitch/openvswitch_2.3.99.bb
recipes-sdn/openvswitch/openvswitch_2.3.0.bb
longer story, to be discussed seperately
recipes-support/lm_sensors/lmsensors_3.3.3.bb
recipes-support/lm_sensors/lmsensors-config_1.0.bb
newer version available from https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-support/lm_sensors/lmsensors_3.3.5.bb
recipes-support/vlan/vlan_1.9.bb
deprecated, iproute2 should be used instead. if really needed, it's still available at
https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-connectivity/vlan/vlan_1.9.bb
recipes-support/net-snmp/net-snmp_5.7.3.bb
outdated recipe at https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.1.bb
should be updated upstream and subsequently de-duplicated.
recipes-support/tcpdump/tcpdump_4.6.2.bb
outdated recipe at https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-support/tcpdump/tcpdump_4.6.1.bb
should be updated upstream and subsequently de-duplicated.
recipes-support/lvm2/lvm2_2.02.132.bb
well, that was me :)
recipes-support/fuse/fuse_2.9.3.bb
duplicate of https://github.com/openembedded/meta-openembedded/blob/fido/meta-filesystems/recipes-support/fuse/fuse_2.9.3.bb
recipes-support/libnetconf/libnetconf_0.6.0.bb
recipes-support/vim/vim_7.4.373.bb
recipes-support/dnsmasq/dnsmasq_2.55.bb
newer version available at https://github.com/openembedded/meta-openembedded/blob/fido/meta-networking/recipes-support/dnsmasq/dnsmasq_2.72.bb
!!! RFC: this recipe installs dnsmasq to /usr/sbin/, however, libvirt and others expect it to live in /usr/bin/, see
http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/recipes-extended/libvirt/libvirt_1.2.12.bb?h=fido#n46
vs.
https://github.com/carosio/meta-caros/blob/master/recipes-support/dnsmasq/dnsmasq.inc#L27
recipes-support/mysql/mariadb_5.5.43.bb
recipes-support/mysql/mariadb-native_5.5.43.bb
outdated recipe at https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-support/mysql/mariadb_5.5.41.bb
should be updated upstream and subsequently de-duplicated.
recipes-support/spidermonkey/spidermonkey_1.8.5.bb
should be replaced by https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-extended/mozjs/mozjs_17.0.0.bb
recipes-support/postgresql/postgresql_9.3.1.bb
ouch. both this, and the meta-oe recipe
should be replaced by https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-support/postgresql/postgresql_9.2.4.bb
are quite outdated...
recipes-support/glusterfs/glusterfs_3.7.1.bb
outdated build also in meta-openstrack, need to decide if we want openstack at all or not...
http://git.yoctoproject.org/cgit/cgit.cgi/meta-cloud-services/tree/meta-openstack/recipes-extended/glusterfs/glusterfs_3.4.2.bb
recipes-support/pv/pv_1.5.3.bb
duplicate of https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-support/pv/pv_1.5.3.bb
recipes-support/liburcu/liburcu_0.8.7.bb
duplicate of https://github.com/openembedded/openembedded-core/blob/fido/meta/recipes-support/liburcu/liburcu_0.8.6.bb
(0.8.7 is already in oe-core/master)
recipes-support/libpcap/libpcap_1.6.2.bb
duplicate of https://github.com/openembedded/openembedded-core/blob/fido/meta/recipes-connectivity/libpcap/libpcap_1.6.2.bb
recipes-support/zeromq/zeromq_2.1.11.bb
version 4 recipe available at
https://github.com/openembedded/meta-openembedded/blob/fido/meta-oe/recipes-connectivity/zeromq/zeromq_4.0.4.bb
do we need version 2?
The text was updated successfully, but these errors were encountered: