Package Details: tmux-mem-cpu-load-git 3.7.0.r29.gdf71d21-1

Git Clone URL: https://aur.archlinux.org/tmux-mem-cpu-load-git.git (read-only, click to copy)
Package Base: tmux-mem-cpu-load-git
Description: CPU, RAM memory, and load monitor for use with tmux
Upstream URL: https://github.com/thewtex/tmux-mem-cpu-load
Licenses: Apache-2.0
Conflicts: tmux-mem-cpu-load
Provides: tmux-mem-cpu-load
Submitter: dlin
Maintainer: willemw
Last Packager: willemw
Votes: 19
Popularity: 0.016730
First Submitted: 2013-02-19 00:39 (UTC)
Last Updated: 2024-06-08 20:51 (UTC)

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

willemw commented on 2017-08-03 07:08 (UTC)

@falsovsky: Only 'i686' and 'x86_64' are allowed here. For building on ARM, you use the -A/--ignorearch option.

falsovsky commented on 2017-03-26 13:29 (UTC)

Please add the 'aarch64' arch.

dlin commented on 2014-12-03 10:16 (UTC)

I open a discuss on https://wiki.archlinux.org/index.php/Talk:Arch_packaging_standards I wish to keep more arch on arch variable. That will keep the status to let other people know it is workable on such arch.

willemw commented on 2014-12-03 09:37 (UTC)

From the AUR home page https://aur.archlinux.org/ : "Contributed PKGBUILDs must conform to the Arch Packaging Standards otherwise they will be deleted! " This refers to the link I mention in my previous comment (see: only 'i686', 'x86_64' and 'any'), so they make it clear enough. For example, archlinuxarm did mention using "yaourt -A" in one of their installation pages/wikis, which is the correct way to do it, otherwise you have to add 'sh4', etc. to a lot of PKGBUILD files. They have removed "yaourt -A", probably to make documentation general and clean. I am not really bothered if 'sh4' stays in arch=(), it just currently doesn't belong in a clean AUR PKGBUILD file. That's just my opinion.

cippaciong commented on 2014-12-03 09:14 (UTC)

@willemw: I'm not sure you are totally right on this. I had your same idea until some time ago when I made some research on the BBS. It seems that since AUR is 100% user supported you could put in arch any architecture you want. https://bbs.archlinux.org/viewtopic.php?id=153431

willemw commented on 2014-12-02 09:32 (UTC)

The rule for "arch=()": https://wiki.archlinux.org/index.php/Arch_packaging_standards#Architectures (only 'i686', 'x86_64' and 'any'). It's only a very minor issue, however Arch Linux and the AUR only support 'i686' and 'x86_64' architectures. Most of the packages you can build for other architectures (see for example http://archlinuxarm.org/), however the PKGBUILD files don't include these additional architectures in "arch=()". (I may decide to leave my comments here. I don't like to alter comment history.)

dlin commented on 2014-12-01 20:37 (UTC)

Please remove old comment or fixed issues to keep AUR clean. 2014/12/01 2.2.1.r3-2 add gcc-libs back, use install instead of mkdir 2014/12/01 2.2.1.r3 remove 'v' in version and depends 2013/08/18 v2.2.1-1 use pacman 4.1 method to pull git source, added pkgver() For willemw. 1. There is no rule to only use i686,x86_64,any. sh4 is workable arch which I've tested. 2. gcc-libs is required for 'namcap' happy.

willemw commented on 2014-12-01 08:14 (UTC)

Only 'i686', 'x86_64' (and 'any') are allowed in 'arch=' in the AUR. For compiling on other archs one can use the -A or --ignorearch option (see 'man makepkg') or a similar option. Note: 'install -Dm755 ...' is (slightly) preferred to using 'mkdir and 'cp'.

1 2 Next › Last »