Re: Testing out jhbuild
> Here are notes from trying a pretty much from-scratch build of > meta-gnome-core-shell. (I made an effort to remove as many > development packages as possible from my system before doing > this.) Apparently I accidentally hit send in evolution. So, in particular ignore the part at the end where it trails off into incoherence. - Owen ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Testing out jhbuild
To me, the criterion for success is that someone can start from scratch, without knowing much about Linux development and have a working build within an hour or so, without having to babysit it. Any sort of babysitting makes things much longer for everybody, and basically impossible for the novice. Here are notes from trying a pretty much from-scratch build of meta-gnome-core-shell. (I made an effort to remove as many development packages as possible from my system before doing this.) * I'm a bit skeptical of the existence of meta-gnome-core-shell, which, as I understand it, is supposed to contain the set of things that need to be built for gnome-shell to work at runtime - so, e.g., dconf is just a run-time dependency, since the build-time depdendency is just gsettings. But what if I wanted to hack on nautilus or gnome-control-center rather than gnome-shell? Shouldn't we shoot for: jhbuild build jhbuild run working? * I think we need to work on our setup process; if you get jhbuild installed, typing jhbuild produces: jhbuild: could not load config file, /home/otaylor/.jhbuildrc is missing With no help about how to create it. You have figure out to go to the jhbuild source tree and copy sample.jhbuildrc into the right place. Shouldn't we offer to create a .jhbuildrc if it doesn't exist or alternatively, just run without one? * The defaults for checkout and installation directory are: checkout - ~/checkout/gnome install - /opt/gnome these seem rather random and incoherent to me. Is there a reason to do the install into a system directory by default? * Before I even tried to build, I ran a modified version of the gnome-shell build-setup script to install a number of system dependencies that I knew would cause failures. This made sure that the following packages were installed (on Fedora) binutils curl gcc gcc-c++ make automake bison flex gettext git gperf libtool pkgconfig jasper-devel libffi-devellibjpeg-devel libpng-devel libtiff-devel mesa-libGL-devel pam-devel python-devel readline-devel libXdamage-devel icon-naming-utils libtool-ltdl-devel libvorbis-devel libusb1-devel cups-devel db4-devel sane-backends-devel xcb-util-devel * I then ran jhbuild sysdeps. When you just run jhbuild sysdeps and it displays a report, it really should make it clear that by running 'jhbuild sysdeps --install' it can install these system dependencies. It installed: libpulse dbus-1 nspr cairo dbus-glib-1 unique-3.0 mozjs185 webkitgtk-3.0 libnl-1 libproxy-1.0 sqlite3 libxslt nss libdaemon libxml-2.0 * I still was missing quite a few packages needed for a successful build. Things I needed to install were: libffi-devel (glib) texinfo (libIDL) libcurl-devel (liboauth) openssl-devel (liboauth) libacl-devel (gudev) libudev-devel (gudev) libicu-devel (webkit) libXt-devel (webkit) libgdbm-devel (avahi) udisks-devel (gnome-disk-utility) wireless-tools-devel (NetworkManager) libuuid-devel (NetworkManager) ppp-devel (NetworkManager) libXtst-devel (mousetweaks) * 99 modules *** Checking out gnome-common *** [1/99] (~44 for gnome-shell. 66 in main moduleset if I just list gnome-shell) * Stuff I had to add * #!$!@ update conflict in gdk-pixbuf * http://live.gnome.org/Jhbuild Is far too detailed and text-y, and "you can do this or you can do that" And probably should not recommend bootstrap under any circumstances * Problems with result - Ugly cursors - Couldn't connect to GVC - Doesn't seem to be picking up appointments ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
3.1.4 smoketesting available
Sorry for the delay on 3.1.4, it's taking time to work through a variety of issues, and it's my first time. A 3.1.4 moduleset should appear here shortly: http://ftp.gnome.org/pub/GNOME/teams/releng/3.1.4/ Any developers who want to help debug issues, please read: https://live.gnome.org/Smoketesting Substitute 3.1.4 for RELEASE. Of course, the best help is to make sure your modules are green here: http://build.gnome.org/ Currently known issues: https://bugzilla.gnome.org/show_bug.cgi?id=655482 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new jhbuild features: jhbuild sysdeps and partial_build = True
On Fri, Jul 29, 2011 at 11:25 AM, Colin Walters wrote: > > The partial_build code works on any system that simply has pkg-config; > you're just responsible for finding and installing > packages/SDKs/whatever. I misunderstood John's statement, there was indeed a bug that made us still look for PackageKit even if all we were doing is parsing pkg-config; fixed now! ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new jhbuild features: jhbuild sysdeps and partial_build = True
On Fri, Jul 29, 2011 at 12:53 AM, John Stowers wrote: >> In the latest jhbuild, when the "partial_build" key is set (the >> default) we explicitly look at what's installed on the system, and if >> they're new enough, omit them from the build list (unless you have >> built them before). > > This doesn't currently work on non-packagekit system, such as Ubuntu. I > created I didn't mention jhbuild sysdeps --install, which is a different beast. The partial_build code works on any system that simply has pkg-config; you're just responsible for finding and installing packages/SDKs/whatever. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new jhbuild features: jhbuild sysdeps and partial_build = True
On 07/29/2011 01:45 PM, Olav Vitters wrote: > On Fri, Jul 29, 2011 at 01:00:46PM +0200, Stef Walter wrote: >> I can't help but wonder if this is going to cause common problems where >> a system package links against an old version of glib, which will then >> conflict with the glib inside of the jhbuild. I've run into this several >> times when using 'skip'. > > Isn't that avoided when you remove those .la files? True, that could be the case. I'm not actually in this situation right now, but I'll give that a shot next time around. Cheers, Stef ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new jhbuild features: jhbuild sysdeps and partial_build = True
On Fri, Jul 29, 2011 at 01:00:46PM +0200, Stef Walter wrote: > I can't help but wonder if this is going to cause common problems where > a system package links against an old version of glib, which will then > conflict with the glib inside of the jhbuild. I've run into this several > times when using 'skip'. Isn't that avoided when you remove those .la files? -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new jhbuild features: jhbuild sysdeps and partial_build = True
On 07/28/2011 11:49 PM, Colin Walters wrote: > In the latest jhbuild, when the "partial_build" key is set (the > default) we explicitly look at what's installed on the system, and if > they're new enough, omit them from the build list (unless you have > built them before). > > You can better understand what jhbuild is doing by looking at the > output of the new "sysdeps" command, like this: Nice :) I can't help but wonder if this is going to cause common problems where a system package links against an old version of glib, which will then conflict with the glib inside of the jhbuild. I've run into this several times when using 'skip'. I haven't seen the problem with the new jhbuild, but I'll let you know if it occurs. Cheers, Stef ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new jhbuild features: jhbuild sysdeps and partial_build = True
On 29 July 2011 05:53, John Stowers wrote: > This doesn't currently work on non-packagekit system, such as Ubuntu. I > created You can use PackageKit on Ubuntu, it works fine. It's just not installed by default, which is unfortunate. Richard. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
