I build uzbl (a webkit-based browser) from the git version, but I pull in the dependancies, including webkit-gtk, via portage. A bit of explanation first. uzbl has 2 options... 1) webkit-gtk-1.x combined with gtk+-2.x 2) webkit-gtk-2.x combined with gtk+-3.x
To view Youtube and other Flash sites, you need Flash (dohhh). Flash is a gtk2 app, and does not work with gtk3. So I need option 1) above, which I force via a "local.mk" file. I have it working on machine A, so I go to machine B. On machine B, the uzbl git build swears up and down that it can't find webkit-gtk-1.x, and fails. I compare the 2 machines. On machine A, I apparently emerged net-libs/webkit-gtk-1.8.3-r201:2 whilst I had emerged net-libs/webkit-gtk-1.8.3-r300:3 on machine B. So I switched machine B over to net-libs/webkit-gtk-1.8.3-r201:2 and uzbl built fine, and works. Now for the question... I had always thought that it was the major version number of the ebuild that determined the major version number of the package, not a weird extension attached to the end of the version number of the ebuild. What gives? -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
