<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 13, 2017 at 12:34 AM, Alejandro Hernandez <span dir="ltr"><<a href="mailto:alejandro.hernandez@linux.intel.com" target="_blank">alejandro.hernandez@linux.intel.com</a>></span> wrote:<br><div> </div><div>[snip]</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div><div class="gmail-h5"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote>
<div><br>
</div>
</div>
</div>
</div>
</blockquote></div></div>
Not as far as I know, but so that would work when building something
AND the artifacts, but what if you want to build the artifacts
only?, you would have to build everything else as well wouldn't you?<br></div></blockquote><div><br></div><div>My only feedback was: we could target something that gives the necessary artifacts</div><div>without depending on any other IMAGE_FSTYPES than wic (and I was assuming wic </div><div>is the reason why the patch exists).</div><div><br></div><div>Currently, for example, all "live" artifacts (including rootfs.img) are built first to get a</div><div>wic image created. The same applies with this patch still: one would need to specify</div><div>another image type first to get the artifacts to get wic image type built. Furthermore, that</div><div>image type would give unnecessary build dependencies (depending on your configuration).</div><div><br></div><div><div>It can also be argued whether the build_*_cfg() are needed here because the wic source</div><div>plugins write their own configs.</div></div><div><br></div><div>The desired outcome (IMO) would be independent from "live" (naming wise also).</div><div><br></div><div>-- Mikko</div><div><br></div></div></div></div>