On 11/21/13, 6:40 AM, Phil Blundell wrote:
On Thu, 2013-11-21 at 20:24 +0800, ChenQi wrote:
The purpose is to disable bind in a read-only file system by default.
But if user really wants it, they can set this value to 'yes'.
I'm still struggling a bit to understand the reasoning here. Why would
you install bind in the first place if you didn't want it to be enabled?
Why do people use core-image-sato, and then try to remove python?
Sorry for the snarkiness, but that's what is being avoided here.
I have to send these patches, due to the YP compliance guidelines, which is why
this is an RFC and not something I'm suggesting for the actual oe-core.. (since
the patch it depends on was not accepted.)
--Mark
p.
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
