"Bottazzini, Bruno" <bruno.bottazz...@intel.com> writes: >> > +FILES_${PN}-services-ask-password = "\ >> > + ${rootprefix}/bin/systemd-ask-password \ >> > + ${rootprefix}/bin/systemd-tty-ask-password-agent \ >> > + >> ... >> I think, enumerating services in this kind becomes a maintenance >> nightmare. E.g. you have to check for every future systemd version >> whether service gets listed in a new .wants. Using wildcards can >> simplify this; e.g. see systemd_elito_populate_packages() in >> >> https://www.cvg.de/people/ensc/systemd_216.bbappend > > On your example, wouldn't we have to enumerate the packages too ?
I do not have a catch-all package (like your '${PN}-services-essential'); the subpackages are announced by | PACKAGES_DYNAMIC += "${@systemd_elito_populate_packages(d, True)}" and I add manual RRECOMMENDS in the toplevel machine task recipe. But it should be trivial to add dependencies within the systemd_elito_populate_packages() function; e.g. | d.setVar("RRECOMMENDS_something", ' '.join(map(lambda x: '${PN}-' + x, pkg_info.keys()))); > Where did you get this file ? It is used in our distribution and its roots are before 2012... I never had time to clean it up, especially because it is very controversial (upstream systemd is against splitting units[1]) Enrico Footnotes: [1] http://comments.gmane.org/gmane.linux.redhat.fedora.devel.announce/1450 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core