[sugar] [PATCH] (Incomplete) Activity Launch Feedback

Eben Eliason eben.eliason
Thu May 15 16:03:03 EDT 2008


On Thu, May 15, 2008 at 3:55 PM, Marco Pesenti Gritti
<mpgritti at gmail.com> wrote:
> On Thu, May 15, 2008 at 9:51 PM, Eben Eliason <eben.eliason at gmail.com> wrote:
>> Hey, responding privately for more details on your suggestion. Are you
>> suggesting that I copy the patch onto a laptop direclty (say, via USB)
>> and then apply it to the already installed OS?  Could you give me
>> details on where and how to accomplish this?  Thanks.
>
> Adding the list back because I think it's interesting to discuss ways
> to get experimental patches like this in the build. I guess you won't
> mind.
>
> No. The way the code gets in the build is:
>
> 1 Build a tarball from the git sources
> 2 Build and rpm from the sources
> 3 Joyride build system grabs the rpm and put it on the images.
>
> I suggest we apply your patch as part of step 2. Does that make more sense?

Ummm, maybe.  Do you mean build an rpm from the tarball?  Otherwise,
how do we get the patch into the rpm without actually pushing the
changes to git master?  In any case, I know little about how any of
these steps work. What does your suggestion imply I need to do myself
to make this happen?

And, for that matter, if it's still going to wind up in a joyride
build anyway (instead of run and tested on a few specific laptops with
modified builds), then what advantage does this have over just putting
the experimental patch in master?  It could always be reverted or
cleaned up subsequently.

Thanks!

- Eben



More information about the Sugar-devel mailing list