On 16 June 2012 04:30, Bernie Innocenti <ber...@sugarlabs.org> wrote:
> > * The port of the shell to gobject-introspection will require > > developers to build master of a few GNOME repositories. Even worst, > > the Sugar touch work will require to build gtk+ code which has yet to > > be written > > Ouch. I hope any weird dependencies we have to add for touch support > will be at least optional. > My understanding from Simon that there won't be weird dependencies, just new stuff in gtk+. > > Anyway I consider sugar-build a pragmatic compromise between > > sugar-core and sugar-jhbuild. It's certainly not a wrapper around > > jhbuild. Think of jhbuild more like a tool that we use internally to > > pull and build modules (it can do that work fine and it's less code to > > write and maintain). > > But we already forked jhbuild and wrapped it with something called > sjhbuild. The result isn't particularly pretty, but perhaps you could > fork sugar-jhbuild and implement your ideas directly there. > I could but it would basically just be a remove everything and replace (I detailed that in my answer to Gonzalo). > What I'm trying to avoid here is a solution that adds yet another layer > of indirection between the developer and the code being built. > If you mean jhbuild being that layer of interaction (and if hidden through a somewhat nicer makefile interface), then I agree. That's why medium term I want to get to the omnibus repository. > > [...] > > I've omitted the rest because I basically agree. Same here, I agree with everything I omitted :) Daniel
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
