The most straight forward way would be to add the activites to extra-activities.modules in jhbuild at http://git.sugarlabs.org/projects/sugar-jhbuild/repos/mainline/trees/master/config/modulesets .
This would allow you to run .sugar-jhbuild build extra-activities to pull in the latest activities from git. Once .modules points to a git repo there is no additional maintenance required to keep sugar-jhbuild up to date. Would this be useful? david On Mon, Apr 13, 2009 at 11:38 AM, Bastien <bastiengue...@googlemail.com> wrote: > Luke Faraone <l...@faraone.cc> writes: > >> On Mon, Apr 13, 2009 at 9:45 AM, Bastien <bastiengue...@googlemail.com> >> wrote: >> >> How do I add new activities when using sugar-jhbuild ? >> >> Add them using the sugar-install-bundle command or using the journal. > > Thanks, but that only useful for .xo/.activity packages. > > I have installed additional activities from the git repo, so I don't > have a .xo bundle. > > The advantage I see in running Sugar from sugar-jhbuild is that I can > test the latest flavor of Sugar -- that would be nice to test the latest > Sugar with the latest version of the activities, which is easily done by > using the git repo. > > How you guys are you using the latest Sugar *and* the latest activities? > > -- > Bastien > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
