On 19/12/11 00:15, Josh Andler wrote:
On Sun, Dec 18, 2011 at 1:15 PM, ~suv <suv-sf@...58...> wrote:
On 18/12/11 21:56, Josh Andler wrote:
On Dec 18, 2011 9:37 AM, "Jon Cruz" <jon@...18...> wrote:
On Dec 17, 2011, at 9:07 PM, Josh Andler wrote:
Win7 0.48.2, unhappy. Win7 trunk, unhappy. Ubuntu Precise, unhappy (last tested a month ago). It's an Intuos 2, so no multitouch.
A few more data points.
OS X 10.6.8, XQuartz 2.3.6 = happy happy.
You get to choose your GTK version via Macports if I'm not mistaken.
Not really: MacPorts doesn't allow to freely choose a version of a port, it always installs the latest version from the Portfile.
Ahhh, I was probably confused by when the user I asked about needed to update XQuartz... I thought that was supplied by MacPorts, after looking back at the link, obviously it's not. Just so I know, is MacPorts somewhat like a package management system since it always installs the latest and greatest then?
Yes, like a package manager it helps to install and upgrade packages (ports) and handles the dependencies. It differs though in that it does not install (binary) packages, but builds everything from the sources.
(There is work-in-progress to provide binary packages, but for now those are limited to Snow Leopard, only few in numbers and only with default variants).
Currently, MacPorts has the latest release of Gtk2 (2.24.8): https://trac.macports.org/browser/trunk/dports/gnome/gtk2/Portfile
- the upgrade from 2.22.1 to 2.24.3 happened 9 months ago,
- the upgrade from 2.20.1 to 2.22.0 was 14 months ago
Good to know. So, it forces the upgrade then or can you choose to not upgrade?
It forces the upgrade: default usage is upgrading all outdated ports (i.e. all ports for which the portfile in the shared repository was updated to install a newer version).
You can manually exclude individual ports from upgrading, but this is not recommended (unless really needed e.g. because of a bug) and has to be done every time when upgrading outdated ports after the database is checked for changes. Alternatively you can maintain a local portfile repository to override the shared one and thus keep certain ports at older versions. This sooner or later can get you into dependency hell ;)
~suv