Package Details: st-git 0.9.r11.g9846a56-1

Git Clone URL: https://aur.archlinux.org/st-git.git (read-only, click to copy)
Package Base: st-git
Description: A simple virtual terminal emulator for X.
Upstream URL: https://st.suckless.org
Licenses: MIT
Conflicts: st
Provides: st
Submitter: vesath
Maintainer: Farzat
Last Packager: Farzat
Votes: 50
Popularity: 0.59
First Submitted: 2012-11-30 01:40 (UTC)
Last Updated: 2024-01-22 11:26 (UTC)

Dependencies (4)

Required by (5)

Sources (3)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

rpodgorny commented on 2013-12-02 01:31 (UTC)

ahhh! never mind, my bad! sorry.

rpodgorny commented on 2013-12-02 01:30 (UTC)

this installs the binary to /sbin which violates the /usr move. please fix it, thank you!

vesath commented on 2013-04-10 08:06 (UTC)

Army: Right; I'll push an update in a few minutes.

<deleted-account> commented on 2013-04-10 07:40 (UTC)

Hmm, maybe it's just a makedependency?

vesath commented on 2013-04-10 03:17 (UTC)

Army: Not sure why you/namcap thought libxext is not needed anymore; try compiling without it...

vesath commented on 2013-04-10 03:11 (UTC)

Army: Good job! You convinced me. :)

<deleted-account> commented on 2013-04-09 09:14 (UTC)

> In my opinion, it should be makepkg's job to define a reasonable pkgver default Well, the thing is, it doesn't. The way your PKGBUILD is written, the pkgver doesn't ever get bumped.

vesath commented on 2013-04-07 19:07 (UTC)

In my opinion, it should be makepkg's job to define a reasonable pkgver default, since it pretends to handle VCS sources transparently; adding a custom function in the PKGBUILD adds complexity for little gain. Also, I believe it will fail on machines which do not have git installed (even if git is in the PKGBUILD's makedepends). Additionally, PKGBUILD should not be written differently whether they are meant for the AUR or proper repositories ([core], [extra], [community]); in fact, some people (including me), maintain repositories of AUR packages. The epoch variable serves a purpose there, and I see no reason why the AUR should care whether it is used or not.

<deleted-account> commented on 2013-04-07 18:22 (UTC)

Oh and you should consider adding a pkgver function, so the pkgver is being updated accordingly. On the Wiki https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines#Git there are some suggestions.

<deleted-account> commented on 2013-04-07 18:21 (UTC)

No hard feelings, it was just a suggestion, in case you didn't do it already and liked it the way I did or people like bananagranola, who I think might like my PKGBUILD. But one thing: On the mailing list there was/is a discussion wether or not we should use epoch on the AUR and most people agree we shouldn't use epoch, since this was introduced for the repos in case pacman wouldn't recognzie a package upgrade to be an update. I myself am not completely sure on this matter. I won't use epoch, especially not on a git package. I just want to mention this.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »