This change considerably speeds up building the default target.
As discussed on sugar-devel@, Etoys developers don't work in
jhbuild, and Sugar core developers rarely need to test their
changes against Etoys.
To build Etoys and its dependencies, simply do one of:
./sugar-jhbuild build etoys
./s
On Sun, 2010-04-25 at 20:12 +0200, Sascha Silbe wrote:
> On Sun, Apr 25, 2010 at 01:46:21PM -0400, Bernie Innocenti wrote:
>
> > This change considerably speeds up building the default target.
> > As discussed on sugar-devel@, Etoys developers don't work in
> > jhbuild, and Sugar core developers r
On 25.04.2010, at 20:29, Bernie Innocenti wrote:
>
> On Sun, 2010-04-25 at 20:12 +0200, Sascha Silbe wrote:
>> On Sun, Apr 25, 2010 at 01:46:21PM -0400, Bernie Innocenti wrote:
>>
>>> This change considerably speeds up building the default target.
>>> As discussed on sugar-devel@, Etoys developer
On Sun, Apr 25, 2010 at 08:37:53PM +0200, Bert Freudenberg wrote:
How do I get into the workflow? I submitted an almost working patch
asking for help, got helped, submitted a working one, but now it's
sitting there:
You already got it right - the patch is blocking on me to figure out
what pack
[Repost with fixed-up From address]
On Sun, Apr 25, 2010 at 01:46:21PM -0400, Bernie Innocenti wrote:
This change considerably speeds up building the default target.
As discussed on sugar-devel@, Etoys developers don't work in
jhbuild, and Sugar core developers rarely need to test their
changes
On 25.04.2010, at 20:53, Sascha Silbe wrote:
>
> On Sun, Apr 25, 2010 at 08:37:53PM +0200, Bert Freudenberg wrote:
>
>> How do I get into the workflow? I submitted an almost working patch asking
>> for help, got helped, submitted a working one, but now it's sitting there:
> You already got it ri
6 matches
Mail list logo
