The first reply states which package is required, as does the message generated by cpan which they posted. Unsurprisingly this is also detailed in the module documentation. Regardless of which tool you're using, if you don't known what you're doing or how to use it, the first port of call should always be the documentation.

Hi marto,

The first reply states which package is required, as does the message generated by cpan which they posted.

Having not worked with Slackware or Gtk2::WebKit I admit I'm at a bit of a disadvantage here, but I imagine I'm not the only one. I can't seem to find a Slackware package named something like "webkit-1.0", and I was assuming that when Linicks wrote "I have obviously done a lot of googling, but that reveals for the above issue is all to do with the debian/ubuntu 'apt-get' this and apt-get that etc." he was in the same situation. But of course I might be missing something?

Unsurprisingly this is also detailed in the module documentation.

There appears to be a 1.x and a 2.x series of releases of WebKit, which I'd have to guess might not be compatible with one another, so it's unclear to me if I wanted to build WebKit from source for use with Gtk2::WebKit whether I'd have to download an old 1.x release. I have not yet found any mention of this in the Gtk2::WebKit documentation, which I did have a look at before first posting in this thread. Which detailed documentation are you referring to?

Not only do I think that asking the OP for what solution they ended up using is a pretty normal thing, I'm genuinely curious which exact version of which package(s) Linicks installed to get it working. I feel the thread has been lacking that specificity so far.

Regards,
-- Hauke D

Having not worked with Slackware or Gtk2::WebKit I admit I'm at a bit of a disadvantage here, but I imagine I'm not the only one. I can't seem to find a Slackware package named something like "webkit-1.0"

Slackware traditionally has only a relatively small set of packages (about 1300 in 14.2), you are expected to build and install software not part of Slackware from source. There is SlackBuilds.org, where you can find build scripts for about 6000 more packages. Download the build script and the source, run the build script as root, and you get an installable slackware package that can be installed using installpkg. If the software you want to install is neither available as a Slackware package nor as a SlackBuild script, you are on your own.

Yes, younger package systems using *.deb or *.rpm packages give quite instant results, just type sudo apt-get whatever-you-want or some other variant and you'll get it, including all dependencies. If you just want to use your system as a blackbox and don't intent to learn anything, use them. Slackware does not use or support them, and for good reasons.

A very welcome side effect is that you really learn how your system works. Slackware is - at the first look - a little bit under-documented. Apart from the documentation that comes with the system, there is a Slackbook dated 2005, and another slightly newer beta dated 2012. One of the first things to learn is how to find documentation, i.e. using man, info, and finding things in /usr/doc. Slackware comes with most FAQs and HOWTOs from the Linux documentation project.

I'm quite sure slackware does not have a webkit package, so you want to search slackbuilds.org. And lo and behold, there are several webkit packages for several Slackware releases, including packages combining webkit and GTK.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)