On 02/04/2015 09:04 AM, Bruno Bottazzini wrote:
It wil be able to choose what systemd module to be installed. The final result may get smaller, if the user wanted to. By default it will install the whole systemd which may be big. --- meta/recipes-core/systemd/systemd_218.bb | 1059 ++++++++++++++++++++++++++---- 1 file changed, 914 insertions(+), 145 deletions(-)
This patch will push a lot of maintenance work onto the Yocto systemd maintainer every time there is an upgrade. It's also easy to miss dependencies because of the inter-dependencies that can exist between services.
For items such as systemd-cgls and the tools, a change like this would be maintainable since those items are self-contained. But yanking out the services into separate packages means the maintainer will have to inspect them on each upgrade to make sure they still work.
Would it be sufficient to use PACKAGECONFIG for each of the items that can be disabled via configure? That way the granularity configuration is done by the systemd maintainers rather than the Yocto maintainer.
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
