On Thu, Feb 23, 2012 at 09:26:50AM +0100, Andreas Müller wrote: > On Mon, Feb 20, 2012 at 1:40 PM, Martin Jansa <[email protected]> wrote: > > On Thu, Feb 16, 2012 at 03:02:54AM +0100, Andreas Müller wrote: > >> V1 -> V2: > >> [2] do not check configuration variables for cross and nativesdk > >> [3] rename systemd_package to systemd_generate_package_scripts > >> [6] parse unit files to determine the files to pack > >> [7] create warning if *-systemd package already rdepends > >> it's base package > >> added in V2: > >> [8]-[20] remove obsolet systemd code from recipes (these were used as > >> test cases) > >> [21] dhcp-(relay) test case for multiple systemd packages > >> [22] modified to start service > >> > >> The following tests were performed: > >> * build from scratch with [1]-[7] / run test > >> * build from scratch / apply patches / build -> check buildhistory diff > >> * build from scratch w/o patches / build from scratch with patches -> check > >> buildhistory diff > >> > >> Additional patches were prepared for other recipes inheriting systemd. > >> These are > >> not yet send because they move systemd support from ${PN} to ${PN}-systemd > >> which > >> currently needs modifications on tasks/images. I'd be happy if a common > >> accepted > >> solution would be suggested/implemented (image-feature?). > > > > Today I've noticed one more issue (not sure if it's caused by this > > patchset or not). > > > > Some images are failing for me with: > > For package xserver-nodm-init-systemd SYSTEMD_SERVICE-entry > > xserver-nodm.service does not exist > > from systemd.bbclass:populate_packages_prepend > > > > I guess it's because sstate package: > > sstate-xserver-nodm-init-all-oe-linux-2.0-r13-all-2-2ac030a94ddbd202f54b99c2e32c6312_package.tgz > > > > has only > > package/lib/systemd/system/xserver-nodm.service > > > > but systemd.bbclass:populate_packages_prepend is looking only in ${D} > > (image directory). > > > I prepared V3 and up to now all tests look good. Regarding this issue:
Great! > What is a test case to reproduce if the modification are OK? With clean tmpdir (and without rmwork) build xserver-nodm to populate sstate-cache, then delete tmpdir and build it again. If it reuses .ipk directly from sstate deploy-ipk.tgz, then it's a bit harder and you have to change checksum of some runtime dependency (so that do_package_write is reexecuted after unpacking package.tgz from sstate) this is usually triggered by change of MACHINE. But if you don't manage to reproduce it then we can fix this in followup.. Cheers, -- Martin 'JaMa' Jansa jabber: [email protected]
signature.asc
Description: Digital signature
_______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
