Package Details: surf-git 0.6.52.g285cc38-1

Git Clone URL: https://aur.archlinux.org/surf-git.git (read-only)
Package Base: surf-git
Description: a WebKit based browser
Upstream URL: http://surf.suckless.org/
Licenses: custom:MIT/X
Conflicts: surf
Provides: surf
Submitter: None
Maintainer: sekret
Last Packager: sekret
Votes: 29
Popularity: 0.000148
First Submitted: 2013-03-06 09:28
Last Updated: 2015-07-23 09:07

Required by (0)

Sources (2)

Latest Comments

zcal commented on 2015-12-10 19:01

Ah, silly me. Thanks!

sekret commented on 2015-12-10 17:30

Yes it does. By default the config.h is being ignored. But if you take a look at the prepare() function you'll see that I commented the line which changes this behavior.

zcal commented on 2015-12-10 16:59

config.h appears to get ignored when the package is built.

sekret commented on 2014-07-02 07:43

Changed the pkgver to something more appropriate and changed the prepare function, because the previous one was ugly and failed if SRCDEST was set in /etc/makepkg.conf to a custom directory (which I have now, that's why I noticed).

sekret commented on 2013-08-13 17:50

Adopted and changed optional dependency xterm to st, since that's the default now.

I'm not sure about the prepare function, but it seems to work fine, so I'll leave it as it is for now.

Anonymous comment on 2013-07-13 19:06

Added xorg-xprop to the dependencies, because of the report in this thread https://bbs.archlinux.org/viewtopic.php?pid=1299773#p1299773 Apparently namcap isn't always right ;)

Anonymous comment on 2013-04-05 21:35

Oh and I changed the way it applies patches. Now it does it how upstream wants it to be done, see http://surf.suckless.org/patches/

Anonymous comment on 2013-04-05 21:35

Ok, I gave my best changing this package to how pacman 4.1 wants it. Please test it and report issues, especially if there's something I can improve on the PKGBUILD, since there's no prototype PKGBUILD in the abs package.

Anonymous comment on 2013-03-22 23:58

Well I could comment the lines which do the patching.

Fact is, I won't be able to make a PKGBUILD which works for everybody. The easiest thing would be, if everyone took the PKGBUILD from here and adjusts it to his needs. I won't do a lot of updates, since it's a git package and the build mechanism is very strait forward, it won't change much, or won't change at all.

eworm commented on 2013-03-22 15:17

For me using SRCDEST is really a bad idea... Your PKGBUILD tries to apply any patch found there - and that's a lot for me.

All comments