silbe pointed out how this is somewhat similar to alsroot "Support isolated start" patches.
I don't like how those patches are setting environment variables inside the sugar script. It's not necessary for the normal case (when things are installed in the system prefix), it's more of a development convenience so I'd rather keep it as something external (it's in jhbuild at the moment, having it in the Makefile is convenient for people which are not using it). Also, fwiw, I don't think sweets stuff should be in sugar. It sounds like some kind of alternative packaging framework and we don't have, say, fedora spec files in sugar git. Marco On 7 December 2011 18:12, Marco Pesenti Gritti <ma...@marcopg.org> wrote: > This allows to run sugar from outside the system path for > development purpouses. > > Signed-off-by: Marco Pesenti Gritti <ma...@marcopg.org> > --- > Makefile.am | 9 +++++++++ > 1 files changed, 9 insertions(+), 0 deletions(-) > > diff --git a/Makefile.am b/Makefile.am > index 9e252af..97992be 100644 > --- a/Makefile.am > +++ b/Makefile.am > @@ -12,3 +12,12 @@ EXTRA_DIST = \ > intltool-extract.in > > DISTCHECK_CONFIGURE_FLAGS = --disable-update-mimedb > + > +run: > + PATH=$(prefix)/bin:$(PATH) \ > + PYTHONPATH=$(pythondir) \ > + XDG_DATA_DIRS=$(datadir) \ > + GTK_PATH=$(libdir)/gtk-2.0 \ > + GTK_DATA_PREFIX=$(prefix) \ > + GI_TYPELIB_PATH=$(libdir)/girepository-1.0 \ > + sugar-emulator > -- > 1.7.7.3 > _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
