* Andre McCurdy <armccu...@gmail.com> [150113 01:57]:
> +# TODO: logrotate 3.8.8 adds autotools/automake support, update recipe to
> use it.
> +# TODO: Document coreutils dependency. Why not RDEPENDS? Why not busybox?
It might well be worth adding autotools support right now.
> DEPENDS="coreutils popt"
> LIC_FILES_CHKSUM = "file://COPYING;md5=18810669f13b87348459e611d31ab760"
> @@ -21,6 +24,9 @@ PACKAGECONFIG ?= "\
> ${@base_contains('DISTRO_FEATURES', 'selinux', 'selinux', '', d)} \
> "
> +PACKAGECONFIG[acl] = ",,acl"
> +PACKAGECONFIG[selinux] = ",,libselinux"
The problem with these two lines, are that you're not explicitly
enabling and disabling those two features; thus our builds won't be
deterministic.
Depending on how the actual tests are performed in the logrotate
sources, it might happen that you're enabling the features just by
making sure that they're going to be built prior to logrotate. Though,
there's no guarantee that this will work (without looking at the source
code).
However, if that enabling works, then we have the problem that the
features will always be activated regardless of whether we add acl and
selinux to PACKAGECONFIG, if these exists in the sysroot. Thus, the
build is undeterministic.
Could you please look at enabling / disabling those features explicitly?
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
