<div dir="ltr">On 20 May 2013 10:48, Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="im">On 20 May 2013 10:12, Simon Schampijer <span dir="ltr"><<a href="mailto:simon@schampijer.de" target="_blank">simon@schampijer.de</a>></span> wrote:<br></div><div class="gmail_extra"><div class="gmail_quote">
<div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I had a sugar-build repo before the osbuild change. I did a git pull in my sugar-build directory and then run ./osbuild help.<br>
<br>
I got the following:<br>
<br>
[erikos@t61 sugar-build]$ ./osbuild --help<br>
Installing virtualenv...<br>
Done.<br>
/home/erikos/sugar-build/<u></u>build/out/sandbox/install/bin/<u></u>python: can't open file '/home/erikos/sugar-build/<u></u>build/commands/--help': [Errno 2] No such file or directory<br>
[erikos@t61 sugar-build]$<br></blockquote><div><br></div></div><div>Looks like a bug, will fix.<br></div><div class="im"><div></div></div></div></div></div></blockquote><div><br></div><div>I made it print a link to the docs (still temporary until <a href="http://developer.sugarlabs.org">developer.sugarlabs.org</a> is up) whenever you pass something which is not a command. I'd rather not maintain two lists of available commands.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im"><div>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
[sugar-build sugar-build]$ ./osbuild pull<br></blockquote><div><br></div></div><div>Note that you are inside a shell here. You should just "pull". (I wonder if the docs are wrong now). That *might* actually break things so we should probably check and refuse to run osbuild inside a shell. <br>
<br></div></div></div></div></blockquote><div><br></div><div>I made it complain. Also the docs looks fine in this respect to me but if you find any place where it suggest to run osbuild inside a shell let me know.<br></div>
<div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div>[sugar-build sugar-build]$ ./osbuild build<br>
<div><div class="h5"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
= Clean =<br>
<br>
* Emptying install directory<br>
* Cleaning automake<br>
* Cleaning glib<br>
* Cleaning gobject-introspection<br>
* Cleaning pygobject<br>
* Cleaning dbus-python<br>
* Cleaning libsoup<br>
* Cleaning webkitgtk<br>
* Cleaning gwebsockets<br>
* Cleaning node<br>
* Cleaning grunt-cli<br>
* Cleaning volo<br>
* Cleaning karma<br>
* Cleaning jshint<br>
* Cleaning docker<br>
* Cleaning json-format<br>
* Cleaning flake8<br>
* Cleaning sugar-docs<br>
* Cleaning sugar-toolkit-gtk3<br>
* Cleaning sugar<br>
* Cleaning sugar-artwork<br>
* Cleaning sugar-datastore<br>
* Cleaning gst-plugins-espeak<br>
* Cleaning sugar-runner<br>
* Cleaning sugar-html-datastore<br>
* Cleaning sugar-html-template<br>
* Cleaning sugar-html-bus<br>
* Cleaning sugar-html-activity<br>
* Cleaning sugar-html-graphics<br>
* Cleaning browse<br>
* Cleaning chat<br>
* Cleaning read<br>
* Cleaning log<br>
* Cleaning terminal<br>
* Cleaning pippy<br>
* Cleaning imageviewer<br>
* Cleaning jukebox<br>
* Deleting state<br>
<br>
= Pulling =<br>
<br>
* Pulling libsoup<br>
* Pulling webkitgtk<br>
* Pulling gwebsockets<br>
* Pulling node<br>
* Pulling grunt-cli<br>
* Pulling volo<br>
* Pulling karma<br>
* Pulling jshint<br>
* Pulling docker<br>
* Pulling json-format<br>
* Pulling flake8<br>
* Pulling sugar-docs<br>
* Pulling sugar-toolkit-gtk3<br>
* Pulling sugar<br>
<br>
Oh, no it cleans my copy of webkitgtk...? :/<br></blockquote><div><br></div></div></div><div>If you pulled latest sugar-build you will have to rebuild webkitgtk anyway I'm afraid, because of the various changes I made.<br>
<br></div>
<div>I've seen it doing a clean before a build. I need to find a way to reproduce. I have the impression it only happens if the build is actually clean already though (which might have been your case because the build directory has been moved in recent sugar-build), so at least it shouldn't hurt for real.<br>
</div></div></div></div>
</blockquote></div><br></div><div class="gmail_extra">So, we have a mechanism to trigger a full build, by cleaning everything before, when there has been changes that made it necessary. In your case I'd say that mechanism has been triggered correctly, even if not quite intentionally!<br>
<br></div><div class="gmail_extra">Though this mechanism was also incorrectly triggered by a "clean; build". In that case we would clean two times, it wouldn't really change anything but it would be confusing. So I fixed that case now.<br>
<br></div><div class="gmail_extra">Thanks for the great bug report!<br></div></div>