Qutebrowser

Have just updated qutebrowser from 1.5.2 to 1.10.1, you can find it wip.

Mounsier

It's not available on pkgin, using 9.0_current

Mounsier Nope, its in the Work In Progress repo. For now you have to build it from source. Although, if you manually install all dependecies first, the build itself on 4 cores takes less than 5min 😉
Heads-up: I've only enabled support for qt5-qtwebkit as backend. Support for qt5-qtwebengine backend requires an update of the package, ...its huge work.
Let me know if you need instructions to build.

Mounsier

So you're dev for NetBSD??

Mounsier Put it like this, I have a humble list of commits

Qutebrowser updated to 1.10.2 in wip, only supported back-end qt5-qtwebkit due to the mess with qt5-qtwebengine

johnb

Go @pin .
thanks
Waiting for more backends

I was bored...,
wip/qutebrowser updated to 1.11.0 😉

Jay

pin also try swisscow.com for search engine it's fast 😄

johnb

Love & Kisses @pin 😄

johnb

Jay swisscow

Jay

johnb .com works too 🙂

pfr

johnb
I prefer QWANT

If anyone is actually using qutebrowser...
I've pushed an update to wip yesterday fixing CVE-2020-11054, https://mail-index.netbsd.org/pkgsrc-wip-changes/2020/05/12/msg016399.html
Please re-build if you are using it.

Updated to 1.12.0

nia

are you going to commit this?

nia I would like to but, at the moment I've only enabled support for qtwebkit, as qtwebengine is broken.
Upstream plans to drop support for qtwebkit once Qt hits version 6, unless development of qtwebkit gets up-to-date, see https://github.com/qutebrowser/qutebrowser/issues/4039
So, honestly I don't know if I should commit?
Thoughts?
Is anyone working on qtwebengine?

nia

pin I replied to the issue. Looks like funding annulen might be a viable way forward?

nia I saw the comment. Yes, founding annulen could be a solution but, porting qtwebengine also. I know, ...it's a huge mess. Just looking at FreeBSD's amount of patches makes me sick.
The thing is, I've installed Alpine on bare metal just to check and, the browser works much smoother with qtwebengine than it does with qtwebkit ...actually, in general, anything webkit based "eats" my cpu in a way, that makes it nearly unusable.

nia

That might be a mistake in the way we're building it... Chromium and WebEngine need some features that won't be available until NetBSD 10 at least.

nia back to the commit question, I've noticed otter-browser is also using qtwebkit backend and its in pkgsrc proper, so I no longer see why qutebrowser shouldn't?
I could push the package, though I'm a bit afraid of negative reactions.

nia we'll likely be shipping firefox52 alongside newer versions for eternity.

😅

nia might be a mistake in the way we're building it...

qutebrowser, midori, vimb and surf-git, all behave the same on my machine 🙁
Do you also experience this? firefox68 and seamonkey are fine, it only happens with webkit based browsers. Although, IIRC it also happens on Linux 🤔

If you think I should commit qutebrowser, I can do it tomorrow, ...today its not possible as I don't have access to my laptop.

nia Chromium and WebEngine need some features that won't be available until NetBSD 10 at least.

Sorry for going back to this... but, which features are these? Are they available in current?

nia

pin I doubt there will be any, since we'll likely be shipping firefox52 alongside newer versions for eternity.