On Fri, 11 Jan 2019 at 16:53, Burton, Ross <[email protected]> wrote: >> I'm slightly worried that this will break on-target RPM users. Since info is >> commonly enabled during on-target installations to track which packages have >> been installed and what their progress is. >> >> Has it been test that this does not break dnf on the target? > > > Easy fix: make this specific to class-native. > > That's probably sensible even if it doesn't break dnf, because then target > RPM behaves as usual.
I'm not too worried as dnf interacts with rpm via rpm's python API; what rpm prints out should be of no consequence. The extra lines are probably useful for the target as well, since postinsts can fail in various ways there too. If this passes the dnf/rpm tests on the AB, I'd leave it like it is. Alex -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
