Re: jhbuild update required
On 5 September 2012 14:56, Colin Walters wrote: > Hi, > > TL;DR: Run "git pull -r && make install" in your jhbuild checkouts. > > The latest "systemmodules" work has landed in jhbuild; in the default > configuration where modulesets are fetched via HTTP, the new ones will > fail to parse with the old code. Could we get a new jhbuild release then? Some distributions (Debian, Ubuntu, openSUSE) have jhbuild packaged in their repositories. Jeremy ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild update required
On Wed, Sep 5, 2012 at 3:10 PM, Jeremy Bicha wrote: > On 5 September 2012 14:56, Colin Walters wrote: >> Hi, >> >> TL;DR: Run "git pull -r && make install" in your jhbuild checkouts. >> >> The latest "systemmodules" work has landed in jhbuild; in the default >> configuration where modulesets are fetched via HTTP, the new ones will >> fail to parse with the old code. > > Could we get a new jhbuild release then? Some distributions (Debian, > Ubuntu, openSUSE) have jhbuild packaged in their repositories. jhbuild is not meant to be packaged. I'd highly suggest you stop packaging jhbuild. > Jeremy > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list -- Jasper ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild update required
On Wed, 2012-09-05 at 15:13 -0400, Jasper St. Pierre wrote: > On Wed, Sep 5, 2012 at 3:10 PM, Jeremy Bicha wrote: > > On 5 September 2012 14:56, Colin Walters wrote: > >> Hi, > >> > >> TL;DR: Run "git pull -r && make install" in your jhbuild checkouts. > >> > >> The latest "systemmodules" work has landed in jhbuild; in the default > >> configuration where modulesets are fetched via HTTP, the new ones will > >> fail to parse with the old code. > > > > Could we get a new jhbuild release then? Some distributions (Debian, > > Ubuntu, openSUSE) have jhbuild packaged in their repositories. > > jhbuild is not meant to be packaged. I'd highly suggest you stop > packaging jhbuild. Well...there are some good and bad things about packaging jhbuild. The bad thing is that there's often a large lag time before packages are updated. The good thing is it's easier to install. Craig, any thoughts on doing a release? ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild update required
On Wed, 2012-09-05 at 14:56 -0400, Colin Walters wrote: > The upside though is that "jhbuild sysdeps --install" now does a LOT > more. > > For future jhbuild updates we'll try to either add a moduleset version > field that makes this error more obvious, or even better - teach jhbuild > how to auto-update itself. Speaking of this, is there an updated document about how to get started with jhbuild? The "getting started" part of Jhbuild's manual is here: http://developer.gnome.org/jhbuild/unstable/getting-started.html.en But it never mentions the sysdeps command. I used to know that you set up jhbuild by: 1. Installing it / creating the config file 2. jhbuild bootstrap 3. jhbuild build [whatever] But that clearly doesn't work these days :) Federico ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild update required
Colin Walters wrote: > On Wed, 2012-09-05 at 15:13 -0400, Jasper St. Pierre wrote: > > On Wed, Sep 5, 2012 at 3:10 PM, Jeremy Bicha wrote: > > > > > > Could we get a new jhbuild release then? Some distributions (Debian, > > > Ubuntu, openSUSE) have jhbuild packaged in their repositories. > > > > jhbuild is not meant to be packaged. I'd highly suggest you stop > > packaging jhbuild. > > Well...there are some good and bad things about packaging jhbuild. The > bad thing is that there's often a large lag time before packages are > updated. The good thing is it's easier to install. > > Craig, any thoughts on doing a release? I just pushed a 3.5.91 tarball. @Jasper: jhbuild packages can be quite useful to get core dependencies installed (git, autotools, etc.), I'd encourage them. Fred ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild update required
On 5 September 2012 15:13, Jasper St. Pierre wrote: > jhbuild is not meant to be packaged. I'd highly suggest you stop > packaging jhbuild. Yes, you're not the only one to say that. But, I thought a big part of what jhbuild offers is that it makes it relatively easy to try out the bleeding edge of GNOME without having to mess with learning how to ./configure, make, make install (and of course ./configure doesn't work on GNOME packages without running autogen.sh first but how's a beginner to know that?). Requiring a beginner to manually build jhbuild from source defeats that advantage. Also, there's the whole problem of users needing to periodically update their jhbuild manually. Why not let distros handle that like they do every other package? I've always ran jhbuild from the distro package. As long as jhbuild gets regular releases, those releases get packaged, and I use the default network modulesets, I don't see a problem. Jeremy ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild update required
> I used to know that you set up jhbuild by: > > 1. Installing it / creating the config file > 2. jhbuild bootstrap > 3. jhbuild build [whatever] If jhbuild used good default values then we could even get started without creating a config file. See bug #655714 for changing the default of prefix to somewhere in ~. https://bugzilla.gnome.org/show_bug.cgi?id=655714 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: jhbuild update required
On Thu, Sep 6, 2012 at 5:23 AM, Jeremy Bicha wrote: > On 5 September 2012 15:13, Jasper St. Pierre wrote: >> jhbuild is not meant to be packaged. I'd highly suggest you stop >> packaging jhbuild. > > Yes, you're not the only one to say that. But, I thought a big part of > what jhbuild offers is that it makes it relatively easy to try out the > bleeding edge of GNOME without having to mess with learning how to > ./configure, make, make install (and of course ./configure doesn't > work on GNOME packages without running autogen.sh first but how's a > beginner to know that?). Requiring a beginner to manually build > jhbuild from source defeats that advantage. I think initiatives along the lines of build servers generating live CDs or usb mountable images are more what you're looking for. Whether you get past actually installing jhbuild on your system or not, by the package manager or via a git clone, there's no way you will be able to build highlevel modules on the bleeding edge without a little know-how. In other words, the build will fail and you will have to fix it, either by upgrading python, installing some unspoken dependency or by actually meddling in source code during the build and forcing it to build. This is not the case for *some* jhbuild setups, for instance stable release module sets typically have less problems and the jhbuild scripts targeting quartz builds (on OSX) are typically error free. But that's only because those build scripts target very specific module versions for each checkout (or resort to downloading release tarballs directly)... if you build master, you will have problems and you should know how to fix them. You cannot blame jhbuild scripts for this issue, the quality of the jhbuild scripts will not avoid the simple fact that there will always be some disconnection between modules in master between release cycles, those are bugs in the effected modules and are generally fixed during the unstable dev cycle (for instance, you cant expect gedit developers to update all of their dependencies between every single commit that they make, although I'm sure they are pretty good at updating things frequently enough). This does not mean jhbuild is not useful, by far. For some perspective, how I used to build gnome modules before jhbuild existed was an exercise consisting of listing by hand all of my inter-module dependencies and updating/building them by hand in the right order. Like many others I would use a custom environment script which consisted mostly of: PATH=/opt/devel/bin:$(PATH) LD_LIBRARY_PATH=/opt/devel/lib PKG_CONFIG_PATH=/opt/devel/lib/pkgconfig ACLOCAL_FLAGS="-I /opt/devel/share/aclocal" (and I probably forgot something else here...) This manual building is a real problem that jhbuild does solve. Cheers, -Tristan > > Also, there's the whole problem of users needing to periodically > update their jhbuild manually. Why not let distros handle that like > they do every other package? > > I've always ran jhbuild from the distro package. As long as jhbuild > gets regular releases, those releases get packaged, and I use the > default network modulesets, I don't see a problem. > > Jeremy > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
