Re: [Gtk-osx-users] GTK updates.

[John Ralls <jralls ceridwen us>]

On Jun 17, 2011, at 12:37 PM, Pascal wrote:

> Hello.
> 
> I wonder when and how to update a current GTK-OSX install.
> 
> I've install it on April the 14th. I don't know if I should expect a new release ;-)
> In fact I wonder how to know when to update GTK.
> Is there a way to know?
> Is there some release notes?
> 
> Then how to do it?
> 
> The instructions for installation were:
> $ sh gtk-osx-build-setup.sh 
> $ jhbuild bootstrap
> $ jhbuild build meta-gtk-osx-bootstrap
> $ jhbuild build meta-gtk-osx-core
> 
> Do I need to repeat them all?
> 
> Thanks for clarification, Pascal.
> http://blady.pagesperso-orange.fr
> 


When to upgrade is completely dependent upon what you need. See below.
Nope.
Nope.
Maybe.

As long as your application builds and runs, there's no point in upgrading, eh? The stable modulesets are still building Gtk+-2.24, which is in maintenance mode: Only critical bugs are being worked upon. There are no releases of gtk-osx-build. Except for bootstra.modules, everything important changes in the git repository, and both the setup script and the modulesets pull from the repo, so if I change anything, it's immediately live. 

The only reason to run the setup script would be if I make changes to the bootstrap module (which I have done recently) and after looking at the log on Github you decide that those changes will help you. The exception to that rule is when I move something into bootstrap which changes dependencies. I just added readline last week, but it may move back out. Other than that, there's nothing that will break if you use the old bootstrap.modules. (If you're working on a PyGtk-based package, you'll wind up building Python twice because I just took it out of bootstrap.modules and moved it to gtk-osx-python.modules. Aside from that, just run jhbuild build meta-gtk-osx-bootstrap meta-gtk-osx-core (and whatever other modules you need) and jhbuild will update the stuff that's been updated and skip the rest.

That said, it's quite possible for the configurations of packages to get confused during an upgrade and for the whole process to fail with weird errors. When that happens, the quickest way to fix it is to delete both the checkoutdir and prefix and to start over from jhbuild bootstrap.

Regards,
John Ralls