Hm the wiki indicates in https://wiki.archlinux.org/index.php/PKGBUILD#arch that "any" would be incorrect. It's always been annoying how arch=() isn't scalable or really even useful... Eventually x86_64 was just added to everything and maybe many years from now arm will be too.
Search Criteria
Package Details: znc-clientbuffer-git r17.8691abf-1
| Git Clone URL: | https://aur.archlinux.org/znc-clientbuffer-git.git (read-only) |
|---|---|
| Package Base: | znc-clientbuffer-git |
| Description: | ZNC module for client specific buffers |
| Upstream URL: | https://github.com/jpnurmi/znc-clientbuffer |
| Licenses: | |
| Submitter: | arcnmx |
| Maintainer: | arcnmx |
| Last Packager: | arcnmx |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2016-08-11 18:08 |
| Last Updated: | 2017-09-06 22:17 |
Required by (0)
Sources (1)
Latest Comments
arcnmx commented on 2017-09-06 22:11
aphirst commented on 2017-09-06 21:51
Since it's possible to install this package on platforms other than just i686 and x86_64, indeed on any for which znc is available, could this possibly be reflected in the PKGBUILD? I have to keep adding armv7h to mine, or keep changing to 'any', which is starting to get frustrating, and I struggle to think I'm the only one.