Re: [Sugar-devel] sugar-build after osbuild change report

2013-05-21 Thread Simon Schampijer
On 05/20/2013 07:43 PM, Simon Schampijer wrote: On 05/20/2013 05:52 PM, Daniel Narvaez wrote: On 20 May 2013 12:48, Daniel Narvaez dwnarv...@gmail.com wrote: Ok, great. Would be fantastic if '--help' would print the list of possible arguments. I'd like to avoid maintaining the docs in

Re: [Sugar-devel] sugar-build after osbuild change report

2013-05-21 Thread Daniel Narvaez
On 21 May 2013 10:15, Simon Schampijer si...@schampijer.de wrote: Pulling today I got: [erikos@t61 sugar-build]$ ./osbuild pull = Updating build system = * Pulling sugar-build Already up-to-date. = Pulling = * Pulling automake * Pulling glib * Pulling gobject-introspection *

Re: [Sugar-devel] sugar-build after osbuild change report

2013-05-20 Thread Daniel Narvaez
On 20 May 2013 10:12, Simon Schampijer si...@schampijer.de wrote: Hi, 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. I got the following: [erikos@t61 sugar-build]$ ./osbuild --help Installing virtualenv...

Re: [Sugar-devel] sugar-build after osbuild change report

2013-05-20 Thread Daniel Narvaez
On 20 May 2013 10:48, Daniel Narvaez dwnarv...@gmail.com wrote: On 20 May 2013 10:12, Simon Schampijer si...@schampijer.de wrote: Hi, 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. I got the following:

Re: [Sugar-devel] sugar-build after osbuild change report

2013-05-20 Thread Simon Schampijer
On 05/20/2013 10:48 AM, Daniel Narvaez wrote: On 20 May 2013 10:12, Simon Schampijer si...@schampijer.de wrote: Hi, 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. I got the following: [erikos@t61 sugar-build]$

Re: [Sugar-devel] sugar-build after osbuild change report

2013-05-20 Thread Daniel Narvaez
On 20 May 2013 12:17, Simon Schampijer si...@schampijer.de wrote: How about we print here something like: You are in a shell now, run commands like 'build' or 'run' here directly. Yeah, that's more or less what I've done.

Re: [Sugar-devel] sugar-build after osbuild change report

2013-05-20 Thread Manuel QuiƱones
2013/5/20 Daniel Narvaez dwnarv...@gmail.com: On 20 May 2013 12:17, Simon Schampijer si...@schampijer.de wrote: How about we print here something like: You are in a shell now, run commands like 'build' or 'run' here directly. Yeah, that's more or less what I've done.

Re: [Sugar-devel] sugar-build after osbuild change report

2013-05-20 Thread Daniel Narvaez
On 20 May 2013 13:55, Manuel QuiƱones ma...@laptop.org wrote: Why does that bother you? :) I mean there is just a single build directory there and everything else is source. Which is the opposite of before, with a source dir and everything else being build script. I'd argue the main

Re: [Sugar-devel] sugar-build after osbuild change report

2013-05-20 Thread Daniel Narvaez
On 20 May 2013 12:48, Daniel Narvaez dwnarv...@gmail.com wrote: Ok, great. Would be fantastic if '--help' would print the list of possible arguments. I'd like to avoid maintaining the docs in two places :) Though perhaps using docker we can figure out something to have both --help and the

Re: [Sugar-devel] sugar-build after osbuild change report

2013-05-20 Thread Simon Schampijer
On 05/20/2013 05:52 PM, Daniel Narvaez wrote: On 20 May 2013 12:48, Daniel Narvaez dwnarv...@gmail.com wrote: Ok, great. Would be fantastic if '--help' would print the list of possible arguments. I'd like to avoid maintaining the docs in two places :) Though perhaps using docker we can