Prev: TuxOnIce
Next: wxwidgets / truecrypt issues
From: Jim Diamond on 30 Nov 2009 10:06
On 2009-11-03 at 02:34 AST, Robby Workman <newsgroups(a)rlworkman.net> wrote:
> On 2009-10-19, Jim Diamond <Jim.Diamond(a)nospam.AcadiaU.ca> wrote:
>> I want to compile something which requires gtk+ 2.16 or greater.
>>
>> I could compile it into its own location (e.g., /opt/gtk+2), as
>> opposed to upgrading the system gtk+2, but for reasons that you
>> probably aren't interested in, I don't want to do that if I can
>> possibly avoid it.
>>
>> So before I risk clobbering my system, has anyone else here attempted
>> doing that? If so, any words of wisdom?
>
>
> Sure, it's possible, and while it's not trivial, it's not too
> terribly difficult either. Theoretically, gtk is backwards
> compatible, but in practice, that's not always the case. For
> the most part, it's a pretty safe bet though.

In case anyone cares:

On Slackware 13.0 I upgraded to pango-1.26.0, glib2-2.22.2 and
gtk+2-2.18.3 and (so far) everything seems to be OK.

On a Slackware 12.2 system, upgrading to glib2-2.22.2 and gtk+2-2.16.6
sufficed.

Jim
First  |  Prev  | 
Pages: 1 2
Prev: TuxOnIce
Next: wxwidgets / truecrypt issues