nicestep at gmail.com
Sun Jan 30 08:53:09 EST 2011
What I was trying to get across is that while the distro packages are
what most people should be using, they aren't up to the minute. By
installing sugar-jhbuild you can test both the latest Sugar and an
older version that is more likely to be used in the field on the same
box without the two environments interfering with each other. That's
not the easiest point to get across. I also say that most developers
should not use sugar-jhbuild, at least not to begin with.
I'll look at it again when I have a chance.
On Sun, Jan 30, 2011 at 5:57 AM, Sascha Silbe
<sascha-ml-reply-to-2011-1 at silbe.org> wrote:
> Excerpts from James Simmons's message of Sat Jan 29 16:22:49 +0100 2011:
>> The book "Make Your Own Sugar Activities!" has some suggestions on
>> development environments and many other topics:
> In the "What About Using sugar-jhbuild?" section you write:
>>> When you're done you'll have an up to date test environment that you
>>> can run as an alternative to sugar-emulator.
> sugar-jhbuild is an alternative to installing Sugar from distro
> packages, nothing more or less.
> In order to run Sugar inside an already-running desktop system (very
> similar to running Linux inside a VM, just at the desktop system level
> instead of at the operating system level) you can use sugar-emulator, no
> matter how you installed it (distro packages or sugar-jhbuild).
> Similarly, you can run Sugar in "native" mode no matter whether you got
> it from distro packages or using sugar-jhbuild.
> It would be nice if you could clarify this in your book, because this
> misunderstanding has been a major source of confusion in the past (and
> probably still is in the present).
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
More information about the Sugar-devel