<div dir="ltr">On 1 February 2018 at 14:10, Daniel F. Dickinson <span dir="ltr"><<a href="mailto:cshored@thecshore.com" target="_blank">cshored@thecshore.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 01/02/18 08:54 AM, Burton, Ross wrote:<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 1 February 2018 at 13:44, Daniel F. Dickinson <<a href="mailto:cshored@thecshore.com" target="_blank">cshored@thecshore.com</a> <mailto:<a href="mailto:cshored@thecshore.com" target="_blank">cshored@thecshore.com</a>><wbr>> wrote:<br>
<br>
I guess the question is would it be useful to have a flag that chooses<br>
a 'typical' tinyness but can be overridden (I'm think here of<br>
avoiding having to specify huge numbers of PACKAGECONFIGs for a<br>
typical tiny case, when really you want most of the 'normal'<br>
tinyness with some<br>
tweaks. What I'm think is that "tiny" really should just change the<br>
defaults for PACKAGECONFIG etc, but like the defaults can be easily<br>
overridden.<br>
<br>
<br>
Well in the idiomatic way the default would be "all the things are on", so doing a "tiny" build would be just setting PACKAGECONFIG="".<br>
<br>
When we're dealing with tiny configurations you can't really say "and this is what people will want", because that's precisely the problem: you don't know what someone else will want.<br>
<br>
Ross<br>
<br>
</blockquote></span>
Fair enough. Is there a way to distribute a set of package configs and/or package selections (can a packagegroup do packageconfig or does that need to be specified in a different scope (I'm still getting used to openembedded)). "tiny" is a bad choice because it's too generic, but perhaps "meta-tiny-router" "meta-tiny-switch" "meta-tiny-home-device" etc would make sense as mini-layers that could take care of sane defaults for different use cases (assuming the work of splitting packages up more and appropriate tinification PACKAGECONFIGs are either submitted to the appropriate layer or bbappended in various layers)?<br></blockquote><div><br></div><div>A distribution can set other recipe's PACKAGECONFIGs directly:</div><div><br></div><div>PACKAGECONFIG_pn-recipename = "foo bar"</div><div><br></div><div>And distributions are welcome to bundle groups of those into inc files for the user to pull in as required at the distro level.</div><div><br></div><div>Ross </div></div></div></div>