[sugar] [PATCH] (Incomplete) Activity Launch Feedback
Marco Pesenti Gritti
Thu May 15 16:16:30 EDT 2008
On Thu, May 15, 2008 at 10:03 PM, Eben Eliason <eben.eliason at gmail.com> wrote:
> Ummm, maybe. Do you mean build an rpm from the tarball?
Yeah the sources tarball.
> 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?
Nope, but you will need someone to make an rpm for you in any case.
> 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?
Would you actually prefer to run it only on a few specific laptops? I
was thinking that developers community feedback (through joyride)
would be also valuable here.
About advantages. I guess I'm trying to keep master as the reference
source and to push experimental patches somewhere else. As soon as a
patch is in main code repository it's very easy to forget about the
implementation problems it had, especially when swamped with a bunch
of other things.
An alternative would be to sync your repository with master, build the
source tarball from it, and make clear in the rpm spec where the
source is coming from. It's cleaner, but I'm not sure it brings
practical advantages at the moment.
More information about the Sugar-devel