Upgrading gtk+ to 2.16 (or 2.18) in Slackware 13.0
in [Slackware]
|
Prev: TuxOnIce
Next: wxwidgets / truecrypt issues
From: Jim Diamond on 19 Oct 2009 11:01 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? Thanks. Jim
From: Douglas Mayne on 19 Oct 2009 12:06 On Mon, 19 Oct 2009 12:01:02 -0300, Jim Diamond 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? > > Thanks. > Jim > Dropline Gnome 2.26 provides gtk+2-2.16 on top of Slackware 12.2. That works for me; YMMV. Also, it looks like gtk+2-2.18 is available for use as part of the "unstable" branch of several distributions- including Dropline, Debian, ArchLinux, etc. If you are to test it, then it is always a good idea to make backups before making major changes to your system. That way, you have an easy method to restore your system to a known working state. -- Douglas Mayne
From: Jim Diamond on 19 Oct 2009 12:21 On 2009-10-19 at 13:06 ADT, Douglas Mayne <doug(a)localhost.localnet> wrote: > On Mon, 19 Oct 2009 12:01:02 -0300, Jim Diamond 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? >> >> Thanks. > Dropline Gnome 2.26 provides gtk+2-2.16 on top of Slackware 12.2. That > works for me; YMMV. Thanks for the pointer, I haven't looked at dropline in a year or three. > Also, it looks like gtk+2-2.18 is available for use as part of the > "unstable" branch of several distributions- including Dropline, > Debian, ArchLinux, etc. I considered trying 2.18, but was trading off its newness vs. the requirements of the software. > If you are to test it, then it is always a good idea to make backups > before making major changes to your system. That way, you have an easy > method to restore your system to a known working state. Thanks; I think in this case removepkg'ing the updates and installpkg'ing the original Slackware packages might be the way to go. (But perhaps you have knowledge to the contrary.) Cheers. Jim
From: Douglas Mayne on 19 Oct 2009 16:12 On Mon, 19 Oct 2009 13:21:48 -0300, Jim Diamond wrote: > On 2009-10-19 at 13:06 ADT, Douglas Mayne <doug(a)localhost.localnet> wrote: >> On Mon, 19 Oct 2009 12:01:02 -0300, Jim Diamond 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? >>> >>> Thanks. > >> Dropline Gnome 2.26 provides gtk+2-2.16 on top of Slackware 12.2. That >> works for me; YMMV. > Thanks for the pointer, I haven't looked at dropline in a year or three. > >> Also, it looks like gtk+2-2.18 is available for use as part of the >> "unstable" branch of several distributions- including Dropline, >> Debian, ArchLinux, etc. > I considered trying 2.18, but was trading off its newness vs. the > requirements of the software. > >> If you are to test it, then it is always a good idea to make backups >> before making major changes to your system. That way, you have an easy >> method to restore your system to a known working state. > Thanks; I think in this case removepkg'ing the updates and > installpkg'ing the original Slackware packages might be the way to > go. (But perhaps you have knowledge to the contrary.) > > Cheers. > Jim > You're probably right- that is, if you are very careful in limiting what packages are installed. For example, if your problem is solved by installing only gtk+2-2.16 from Dropline, then you could probably use the standard tools to roll the package back to the official Slackware package if necesssary. However, if you start by installing a lot of Dropline Gnome packages, and then end up having to uninstall, it can get very tricky fast. It might not be possible to practically remove it. In that case, having the ability to roll back to a known working state is worth the trouble of making an initial backup. YMMV. -- Douglas Mayne
From: Robby Workman on 3 Nov 2009 01:34
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. -RW |