<br><br><div class="gmail_quote">2011/11/18 Paul Eggleton <span dir="ltr"><<a href="mailto:paul.eggleton@linux.intel.com">paul.eggleton@linux.intel.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Friday 18 November 2011 15:28:28 Frans Meulenbroeks wrote:<br>
> Is ordering of PACKAGES relevant? If so, please enlighten me why.<br>
<br>
</div>It is. The packaging code reads this in order and the first package to match a<br>
file is the package that the file will go into; thus if you want to add a<br>
package that will include files that would normally be in one of the default<br>
packages you need to prepend to PACKAGES so that your new package gets the<br>
files first.<br>
<br></blockquote><div>Ah, ok. understood.<br>Not fully sure if the current behaviour is the most desirable one.<br>Is it still possible to put a file into two packages by explicitly adding it to both?<br><br>Also it might be somewhat confusing that a line that adds say a dir to a package does not necessarily get all fies in that dir in the package <br>
Personally I think I prefer to have all added in that case, irrespective if a previous package already took a file from it.<br>Alternately it could be seen as a QA issue if a file could have been added to two packages (in which case a more strict pattern should have been used somewhere)<br>
<br>Frans<br></div></div>