Midori Webbrowser?
 

What do I need for dependensies to run x86_64 Midori on Slackware 14.1 current?

Search at Slackbuilds.org. They should have a list.

Looking at Slackbuilds, it requires libunique, vala, and webkitgtk (webkitgtk requires gst1-plugins-base (which requires gstreamer which requires orc) and libwebp).

http://slackbuilds.org/repository/14.1/network/midori/

So, you can easily create a build queue using sbopkg's sqg by issuing

And then build the resulting queue using

and then selecting q for queue.

However, if you want to do it manually, the build order could be something like this:

libwebp
orc
gstreamer
gst1-plugins-base
webkitgtk
vala
libunique
midori

Thats nice thank you:)

In my experience, it's not worth it. webkitgtk feels like it takes forever to compile. And then midori always is crashy, whenever I use it.

If you're looking for a lightweight web browser with lower dependency overhead, try dillo or netsurf.

but how do I manage sqg -p midori should I set sbopkg first and then sqg -p midori or what

I have syncted sbopkg repositories, im lost

Well on my system webkitgtk takes 3hrs to build. But newer midori crashes less. I avoid sites heavy in Jscript/images etc. It works well for sane sites.

Webkitgtk and midori is available from Salix.
http://ftp.cc.uoc.gr/pub/dist/salix/...1/PACKAGES.TXT

Simply build your dependencies one after another, using sbopkg.

If you have a multicore CPU and enough RAM, you can edit webkitgtk's SlackBuild file and replace make by make -j3 or make -j5. Take the number of CPU's you have (cat /proc/cpuinfo | grep processor) and add 1 to get the right number. This will speed up your build significantly.

Cheers,

Niki

Can you give me a example how it should look like please, I don´t understand it.

sqg is a part of the sbopkg package. And now that I think of it, I forgot that you need to pull it out of the /usr/doc/sbopkg-0.37.0/contrib/ directory (I wish they'd just include it in /usr/bin automatically). You can either symlink it, or copy/move it (I think I copied it) to /usr/bin yourself. Then you might need to modify the file and change the REPO_BRANCH (line 48) variable to 14.1 (although, it might pull this out of the sbopkg.conf file and may not be necessary to edit).

After that is done, you should be able to run sqg -p midori and follow the rest of my post.

It sucks so he shouldn't bother but if he wants to discover that for himself:

x86_64/14.1/salix/d/orc-0.4.18-x86_64-1gv.txz
x86_64/14.1/salix/l/gst1-plugins-base-1-noarch-1gv.txz
x86_64/14.1/salix/l/gstreamer1-1.2.2-x86_64-1gv.txz
x86_64/14.1/salix/l/libsecret-0.16-x86_64-1gv.txz
x86_64/14.1/salix/l/libwebp-0.3.1-x86_64-1gv.txz
x86_64/14.1/salix/l/webkitgtk-2.2.5-x86_64-1gv.txz
x86_64/14.1/salix/xap/midori-0.5.8-x86_64-2gv.txz

Midori works fine with webkitgtk-1.10.2, which uses gstreamer-0.10 so you dont need the gstreamer1 dependencies.
If you want to use a newer webkit it helps to upgrade cairo to 1.12.18 with that version it crashes a lot less.

I'm a long time midori user, it has its quirks but its leightweight and fast.

Now I have it compiling at last, It took a while for the coin to drop down in my brain. Nice to see how long it takes have a six core and 16gB ram and ssd.




It took 90 minutes and it is working perfect. Thank you everyone for your replies.

I don't think most of the slackbuilds are written to take advantage of multiple cores. When compiling really large packages I sometimes edit the slackbuild script and change 'make' to 'make -j16' on my 8 core desktop :)