[OE-core] [PATCH 0/3] pseudo+image.bbclass: changes to avoid host contamination
Peter Seebach
peter.seebach at windriver.com
Mon Oct 13 22:35:45 UTC 2014
On Mon, 13 Oct 2014 17:29:26 -0500
"Peter A. Bigot" <pab at pabigot.com> wrote:
> Basically, even if "root" is a special case, taking this path means
> making assumptions about what the application is doing based on what
> system/libc functions it invokes. Too often when somebody assumes a
> general tool will only be used specific ways, somebody else will prove
> them wrong.
True.
For the oe-core case, it seems like it might be reasonable for us to set
pseudo up to, by default, get configured with preloaded things which match
the expected configuration of base-passwd. If people then go overriding
base-passwd in strange ways, they could break that, but we at least know what
the default configuration would be, and could possibly even make base-passwd
check whether pseudo's configuration matches its answers, and blow up if
there's a mismatch there.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
More information about the Openembedded-core
mailing list