<p dir="ltr">You are asking for a flag to be added in ubuntu-image, and ignoring anything I say about potential problems and ideas to solve it. You simply cannot tell how much time it would take to implement the proper solution because we've been talking across each other instead of having a productive conversation.</p>
<p dir="ltr">Today it's a pseudo national holiday for me, but I will try to talk to Barry and Steve tomorrow.<br>
</p>
<div class="gmail_extra"><br><div class="gmail_quote">On Oct 12, 2016 4:15 PM, "Oliver Grawert" <<a href="mailto:ogra@ubuntu.com">ogra@ubuntu.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi,<br>
On Mi, 2016-10-12 at 16:04 -0300, Gustavo Niemeyer wrote:<br>
> We've discussed multiple times in meetings and threads that we want<br>
> to represent the content of the images accurately inside gadget.yaml.<br>
> The fact we're not yet doing that is a bug that we need to fix, and<br>
> if there's disagreement we should talk about it.<br>
> The whole point of redesigning these tools is to evolve the status<br>
> quo towards something we are aiming at with underlying goals. If we<br>
> are going to rush it in, we can just pick up the tooling we had (or<br>
> the hack you mention) and put the images out.<br>
><br>
<br>
well, why cant we do both and unblock others that are waiting ?<br>
<br>
as i said, the images wont regress to what we have today if barry<br>
implements this bit, but people in foundations can finally start to<br>
work on the cdimage side ...<br>
<br>
if you think it is a release critical bug, we should hold the release<br>
for it, we got still enough image related issues to solve that will<br>
already fill the next weeks.<br>
<br>
nobody wants to rush in anything nor will anything discussed cause any<br>
regression over the status quo.<br>
<br>
ciao<br>
oli</blockquote></div></div>