<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 4, 2016, at 12:53 PM, Burton, Ross <<a href="mailto:ross.burton@intel.com" class="">ross.burton@intel.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On 4 January 2016 at 18:36, Khem Raj <span dir="ltr" class=""><<a href="mailto:raj.khem@gmail.com" target="_blank" class="">raj.khem@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":382" class="a3s" style="overflow:hidden">Would it thow some sensible configure errors on enabling importd<br class="">
without the dependencies ? now that they are packageconfigs on their<br class="">
own. ?</div></blockquote></div><br class="">No, basically currently if you enable enough options then importd enables itself so the main aim here was to add some determinism to both all the compression backends and importd.</div><div class="gmail_extra"><br class=""></div></div></div></blockquote><div><br class=""></div><div>OK thank you.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra">Ross</div></div>
</div></blockquote></div><br class=""></body></html>