Package Details: qutebrowser-git 0.10.1.r74.gdfb4374ae-1

Git Clone URL: https://aur.archlinux.org/qutebrowser-git.git (read-only)
Package Base: qutebrowser-git
Description: A keyboard-driven, vim-like browser based on PyQt5 and QtWebKit
Upstream URL: http://www.qutebrowser.org/
Licenses: GPL
Conflicts: qutebrowser
Provides: qutebrowser
Submitter: The-Compiler
Maintainer: The-Compiler
Last Packager: The-Compiler
Votes: 53
Popularity: 2.542114
First Submitted: 2014-11-11 21:47
Last Updated: 2017-03-08 06:36

Latest Comments

The-Compiler commented on 2017-03-15 19:31

buttcake: No - it's not required, and the scenario is too uncommon to even add it as an optional dependency.

buttcake commented on 2017-03-15 19:29

Shouldn't this require python-opengl as of https://github.com/qutebrowser/qutebrowser/commit/85fff35eefcd8d8855a77939a303afd702e3ed5b ?

The-Compiler commented on 2017-03-07 07:00

Sorry this took so long - but the repo URL is now up-to-date (not that it'd make any difference :P), the pkgver check for qt5-webkit is removed, and userscripts are installed so that ":spawn -u" works for the ones in the repo.

As for the pkgver, I want to wait until v0.10.1 so I can test how to handle the tags correctly, see https://github.com/qutebrowser/qutebrowser/issues/2411

hero commented on 2017-02-17 07:43

I second lucc's request to change the pkgver(). From https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git you can see, that it is recommended to use the following for packages with tags:
pkgver() {
cd "$pkgname"
# cutting off 'v' prefix that presents in the git tag
git describe --long | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g'
}
This provides something in the likes of 0.9.0.r277.g79d22f250

I have not tested, if it demands to increment the pkgrel.

lucc commented on 2017-02-07 09:06

Could you use "git describe" in pkgver(). It has the advantage to include tag names into the output and hence the version number of aur/qutebrowser-git would better compare to the one of commuinty/qutebrowser.

For comparison, I get these kinds of version strings from other packages (pacman -Q|grep -e '-git '):
afew-git 1:0.242.b19a88f-1
i3pystatus-git 3.35.r179.g82555cb-1
mblaze-git r486.113445d-1
qutebrowser-git r11145.e487fe441-1
texlive-localmanager-git 0.5.1.r0.g6befd1e-1
vimpager-git 2.06.r337.ga7d18ce-1
zsh-history-substring-search-git 1:117.aae3388-1

It also seems that you would not even have to update (use) the epoch of the package as pacsort is happy to consider the new format I imagine a newer version. I tried this by updating the pkgver() like this (and some other variants):
pkgver() {
cd "$srcdir/qutebrowser"
local ver=$(git describe)
ver=${ver#v}
ver=${ver/-/.r}
ver=${ver/-g/.}
printf %s "$ver"
}
then executed makepkg and finally ask pacsort what it considers the newest version:
$ ls qute*xz|pacsort
qutebrowser-git-r11138.52e386536-1-any.pkg.tar.xz
qutebrowser-git-r11145.e487fe441-1-any.pkg.tar.xz
qutebrowser-git-0.9.0.r183e487fe441-1-any.pkg.tar.xz
qutebrowser-git-0.9.0.r183.e487fe441-1-any.pkg.tar.xz
qutebrowser-git-0.9.0.183.ge487fe441-1-any.pkg.tar.xz

(Please note that the 0.9.0 is due to issue #2284.)

Ambrevar commented on 2017-02-06 12:29

Currently it is not possible to use qutebrowser with the qt5-webkit-ng package because of the versioned dependency of qt5-webkit, forcing users to use the old
insecure qt5-webkit package. Please remove the version from the dependency: qt5-webkit provides "qt5-webkit" as well.

shioyama commented on 2017-02-04 23:51

Please switch to the new official repository: https://github.com/qutebrowser/qutebrowser

lucc commented on 2017-02-02 09:47

Could you also install some things from the misc folder? Especially the userscripts, maybe to /usr/share/qutebrowser/userscripts. And maybe also the cheatsheet to some docs folder. I don't know if any of the other files would be interesting.

The-Compiler commented on 2016-06-07 07:31

@ainola Thanks for the heads-up, done!

ainola commented on 2016-06-07 03:38

Hi, The-Compiler! Pacman now automatically performs post-install hooks so you can safely remove the .install file entirely.

All comments