On 02/17/2014 04:30 AM, Bric wrote:
On 02/16/2014 10:24 PM, Michael Torrie wrote:
On 02/16/2014 04:30 AM, Bric wrote:
Nonetheless, I run ./configure in gtk+ git, and I am still getting
unmet
dependencies:
configure: error: Package requirements (glib-2.0 >= 2.39.5 atk >=
2.7.5 pango >= 1.32.4 cairo >= 1.12.0 cairo-gobject >= 1.12.0
gdk-pixbuf-2.0 >= 2.27.1) were not met:
Requested 'glib-2.0 >= 2.39.5' but version of GLib is 2.32.4
Requested 'atk >= 2.7.5' but version of Atk is 2.4.0
Requested 'pango >= 1.32.4' but version of Pango is 1.30.0
Requested 'gdk-pixbuf-2.0 >= 2.27.1' but version of GdkPixbuf is 2.26.1
________________________
So, this is no longer an ancient system. What do I do? (Aside from
"trashing" this new one with local builds, as I did the old one?)
Never upgrade system versions of glib and gtk+ in place unless you
really know what you're doing. Instead if you need newer versions,
compile them to their own prefix. You can set the PKG_CONFIG_PATH
variable to point to that prefix and ./configure will see them.
Also you can use jhbuild (google for it) to build the latest versions of
gtk+ to its own prefix (say /opt/gtk3).
Thank you.
If you dislike Unity, you can install the mate-desktop, which is a
continuation of the old gnome2 desktop that you are used to.
I do dislike Unity. But I somehow managed to pull gnome back into my
new install, so currently, i am using gnome (you are prompted to
choose among several options, on boot)
To D. Marceau:
I'm going to take a chance and not back up everything. I don't have
space to back up all my stuff right now. One would think that, after
years of developing system installs, Ubuntu won't do me in (outside of
my clicking "erase everything..." during the install because I'm going
on two hours of sleep or something) (Word of caution to others: the
installer wipes out stuff in /usr and /etc, so, for example, I lost a
painstakingly developed xkb configuration file ... painful to no end...)
I think I have to switch a couple of settings in update-manager, no?
Like, broaden the upgrade option to all systems, rather just to
long-term versions. Will be rebooting and re-probing shortly.
I made the mistake the first time around of NOT selecting "download
packages..." during the install. (I had to upgrade from the CD). I am
assuming that would have made the installer better match whatever I
already had, with remote repositories, rather than simply getting rid
of packages it couldn't match with the CD installer. (It's a pain
having to reconstruct everything it wiped out!)
To A. Cottrell:
You are probably right; I should have tried gtk+ 3.0.12 or some such.
I wonder if that would have worked with the old system. And, of
course, you are right about not messing with glib - i had a vague
memory of installing gtk+ on a fedora, years ago, and the memory
didn't involve system trashing, or any risk thereof. So... that's
what you get when you rely on old, vague memories - the world of linux
libraries has been moving on rapidly :-))
FWIF: with this drive to keep upgrading, I just lost a critical hour of
sleep (I start new class material today and needed to be rested) because
I messed up the one and only thing you should NEVER mess up in your
system: network (wifi) connection (if you are out and about and have no
way of plugging into ethernet): With my eye on the 14.04 prize, I
checked "unsupported" and "pre-release" packages in Update Manager, so
it went ahead and installed newer linux-firmware, which screwed up my
wifi connection. Luckily, I was still near an ethernet port, and
downgraded. Again, just a caveat/caution for anyone who might try to
draw from this experience.
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list