<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Jun 8, 2014 at 12:15 AM, Jakob Schwendner <span dir="ltr"><<a href="mailto:jakob.schwendner@dfki.de" target="_blank">jakob.schwendner@dfki.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<div> - one question: should not we split the rock package set into subprojects as well (for me, it is +1, it would make more sense from a management point of view to have a package and its package set in the same organization)<br>
</div><div class="">
<div>
</div>
</div><div>
It seems cleaner to do it this way. But its adding more includes at the manifest, right? Maybe leaving it for now would be ok.</div></div></blockquote><div>Would create a rock package set which would simply auto-import the other ones. But I agree, we can do that later.</div>
<div><br></div><div>Sylvain</div></div></div></div>