I was planning on building both GTK+ and any apps depending on the new version from source. VL was my first Linux, and I started with it back on version 3 before the packaging system was easy to use, and learned to compile from source before I could figure out the packager. So I'm used to building from source. ; )
As far as updating to VL 5.9 goes, I've done a lot of messing around and tweaking things on my computer so far, and I stick with the "don't fix it unless it's broke" strategy. Reinstalling the OS on my desktop seems a bit overkill just to get a slightly newer media player. I'm not even sure it'll do what I want (play mp3s on a remote system with ESound, and NOT speed up playback like XMMS does). That's a lot of fix for a little problem. The last reason I don't want to just install 5.9 is that it wouldn't help me understand my computer or Linux any better. I learn by fiddling around with things.
Headacher: I suspected it would have something to do with using --prefix, but I wasn't sure exactly what directory I should use. If I set it to /usr/local, will that not break my old install? I'm not too worried about figuring out how to get software to compile with it; that's
something I can use trial and error on without breaking anything else. The configure script is already giving me some leads:
checking for GTK... configure: error: Package requirements (gtk+-2.0 >= 2.12.0) were not met.
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively you may set the GTK_CFLAGS and GTK_LIBS environment variables
to avoid the need to call pkg-config. See the pkg-config man page for
As far as pkg-config goes, would it make sense to change it to point to the new version? If currently installed apps don't reference it to find out where GTK+ is, then it shouldn't break the programs already installed...and if I compile new apps, they might as well use the new version, right?