<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jul 8, 2014 at 1:57 PM, Martin Zenzes <span dir="ltr"><<a href="mailto:martin.zenzes@dfki.de" target="_blank">martin.zenzes@dfki.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="">
<br>
<div>On 07/08/2014 01:53 PM, Sylvain Joyeux
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I don't like this, as in most situations people
*want* the GUI. The nogui case is a special case. all packages
including the GUI is the common case. Note that gui/vizkit was
already part of rock.toolchain before the migration.</div>
</blockquote></div>
the embedded guys don't want to have anything to do with gui-stuff.
In my view: keep the minimal depedency-chain as short as possible.
otherwise people will start talking using words like "bloated"</div></blockquote><div><br></div><div>Sorry if I hurt your feelings, but the embedded guys are far from being the "common case". Moreover, if you want to reduce the number of packages you install on your embedded system to a minimum (which is probably what you want), then having a metapackage is not what you are looking for. You want to pick packages one by one.</div>
<div><br></div><div>Now, as a middle ground, where would a rock.core.nogui metapackage not fit the "embedded guy" case ? </div><div> </div><div>Sylvain</div></div></div></div>