[Sugar-devel] IMPORTANT: "sugar-jhbuild run" no longer starts sugar-emulator by default

[Jim Simmons]

Scott,

In the "Make Your Own sugar Activities!" book I'm doing at Floss
Manuals I do refer to "sugar-emulator" as something distinct from
sugar-jhbuild.  For instance, I'll say, "If you're using sugar-jhbuild
under Fedora 11 do this, if you're using sugar-jhbuild do that."  Even
though technically what I call sugar-jhbuild is not completely
different from sugar-emulator the experience of running them is
different.  In earlier versions ./sugar-jhbuild run would use more
recent versions of libraries that were actually installed on the box.

Calling "./sugar-jhbuild run sugar-emulator" just "sugar-jhbuild" is a
convenient way to get people to know what you're referring to, even if
not strictly accurate.

I wasn't aware that "run" had those options.  I don't think it's
documented anywhere.

James Simmons

On Wed, Feb 3, 2010 at 3:42 PM, C. Scott Ananian <cscott at laptop.org> wrote:

>>
>> Are there any other arguments that you could use with "run" other than
>> sugar-emulator?
>
> Yes:
>  jhbuild run make
>  jhbuild run make check
>  jhbuild run python
> etc.
>
> I think it displays exactly the problem Sascha is trying to fix that
> people think that sugar-jhbuild "is" sugar-emulator, instead of (the
> actual case) jhbuild just being a command that sets some environment
> variables and then execs "the real program", be that sugar-emulator or
> make or python or whatever.
>  --scott