@ostroffjh, if it is possible, the separate branch would be good, with large lettered warning that this is bleeding edge alpha build. And that this build might ruin your FAH experience. This was the case with 8.5.1, but 8.5.2 fixes what .1 had broken. I for one, would appreciate the bleeding edge build, since one of the testing platforms for me is Endeavour, and having the latest build would help me a lot, as I seem to hit the brick when I am trying to compile it from github source. Also, keep in mind, that from time to time alpha would become beta, and then become stable, and things would calm down for a while, so at that point you would have stable and alpha sections here having the same build. Due to other commitments FAHclient developments comes in cycles. It happens at rapid pace one minute, and then things settle down for a while :D
Search Criteria
Package Details: foldingathome 1:8.5.5-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/foldingathome.git (read-only, click to copy) |
|---|---|
| Package Base: | foldingathome |
| Description: | A distributed computing project for simulating protein dynamics |
| Upstream URL: | https://foldingathome.org/ |
| Keywords: | fah science |
| Licenses: | GPL-3.0-or-later |
| Submitter: | dtw |
| Maintainer: | PlasticSoup |
| Last Packager: | PlasticSoup |
| Votes: | 184 |
| Popularity: | 1.09 |
| First Submitted: | 2007-06-28 14:55 (UTC) |
| Last Updated: | 2025-12-23 16:05 (UTC) |
Dependencies (16)
- bzip2 (bzip2-gitAUR)
- expat (expat-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-eacAUR, glibc-git-native-pgoAUR)
- lz4 (lz4-gitAUR)
- openssl (openssl-gitAUR, openssl-aegisAUR, openssl-staticAUR)
- re2 (re2-gitAUR)
- sqlite (sqlite-fossilAUR)
- systemd-libs (systemd-libs-selinuxAUR, systemd-libs-gitAUR)
- zlib (zlib-gitAUR, zlib-ng-compat-gitAUR, zlib-ng-compat)
- git (git-gitAUR, git-glAUR) (make)
- leveldb (leveldb-gitAUR) (make)
- libyaml (libyaml-gitAUR) (make)
- scons (make)
- snappy (snappy-gitAUR) (make)
- opencl-driver (opencl-nvidia-410xxAUR, amdapp-sdkAUR, opencl-nvidia-440xxAUR, vc4cl-gitAUR, opencl-nvidia-430xxAUR, beignet-gitAUR, intel-openclAUR, mesa-wsl2-gitAUR, opencl-nvidia-340xxAUR, opencl-legacy-amdgpu-proAUR, beignetAUR, opencl-510xx-nvidiaAUR, intel-compute-runtime-legacyAUR, intel-compute-runtime-legacy-binAUR, opencl-nvidia-teslaAUR, opencl-nvidia-470xxAUR, opencl-nvidia-550xxAUR, amdonly-gaming-opencl-rusticl-mesa-gitAUR, opencl-nvidia-390xxAUR, opencl-nvidia-535xxAUR, opencl-nvidia-525xxAUR, opencl-amdAUR, mesa-rk35xx-gitAUR, opencl-nvidia-575xxAUR, intel-compute-runtime-binAUR, intel-compute-runtime-gitAUR, opencl-nvidia-betaAUR, opencl-nvidia-vulkanAUR, rocm-gfx120x-binAUR, rocm-gfx110x-binAUR, rocm-gfx1150-binAUR, rocm-gfx1151-binAUR, clvk-gitAUR, mesa-gitAUR, opencl-mesa-minimal-gitAUR, opencl-nvidia-580xxAUR, intel-compute-runtime, intel-oneapi-compiler-shared-runtime, opencl-mesa, opencl-nvidia, rocm-opencl-runtime) (optional) – GPU support
Required by (0)
Sources (3)
muziqaz commented on 2025-10-11 09:35 (UTC)
ostroffjh commented on 2025-10-08 23:29 (UTC)
If this package is to be rolled back to a stable release, is there any point in creating a separate one for the most recent tagged release, even if known to be unstable? Many packages have a distinct -git package. I've actually been running 8.5.1 for a bit now, with no apparent problems - is this something the foldingathome team wants to hear? I suppose if I want to test pre-release versions, I can do so manually from git clones, but an AUR version certainly makes it easier for me.
PlasticSoup commented on 2025-10-08 23:13 (UTC)
Thank you for the information calxalot. I will roll this back to 8.4.9 and wait for a proper release.
calxalot commented on 2025-10-08 00:24 (UTC) (edited on 2025-10-08 00:26 (UTC) by calxalot)
Tags can be for an alpha, beta, or public release. Presence of a tag does not mean a stable public release. Tags are not given suffixes like "beta" or "dev".
8.5.1 is a broken alpha. Do not use it.
If an alpha is good enough, it may be moved to beta without further changes. If a beta is good, it might become a public release.
Development is effectively being done on the master branch. There is no guarantee that you can build from HEAD, or that result will work.
The change log gets updated periodically using a future version number. Complain to Joseph if you want him to start using an Unreleased section instead.
URLs to watch:
https://foldingathome.org/alpha/
https://foldingathome.org/beta/
https://foldingathome.org/start-folding/
Yes, the 8.4.9 tags should be identical to the last release. Note cbang tags have prefix "bastet-".
PlasticSoup commented on 2025-10-07 23:47 (UTC) (edited on 2025-10-07 23:48 (UTC) by PlasticSoup)
@ostroffjh I think I must have had 8.5.2 in my head because that was the latest version in the change log, but this is pulling the code for the 8.5.1 tag.
@calxalot I updated the PKGBUILD to 8.5.1 tag (the commit this downloads is the one for that tag) as I thought tags were being used in place of "releases" since there are none. It looks like you are a contributor to the project so perhaps you can give me some incite. From your previous comments I take it that tags are not necessarily indicating release ready code. Am I reading that correctly? If so, would it be better for fah users and the project for me to keep this PKGBUILD on whichever version is listed on the foldingathome.org download page? Also, do you know if the 8.4.9 tag is the same code used to build the official packages?
calxalot commented on 2025-10-07 21:55 (UTC)
That makes sense. Subjecting people to a broken alpha release does not.
Anyway, Jeremy needs to fix it.
ostroffjh commented on 2025-10-07 21:48 (UTC)
And the tag associated with that commit is 8.5.1 (I forget whether the tag is set on that actual commit or a previous one.) I just think there was a typo when updating PKGBUILD.
calxalot commented on 2025-10-07 21:46 (UTC)
I see pkgbuild has its own notion of version. It also looks like it checks out by commit, not tag.
calxalot commented on 2025-10-07 21:42 (UTC)
The package version is not determined by the git tag. There is a package.json with the version number.
ostroffjh commented on 2025-10-07 21:37 (UTC)
but there IS a tag for 8.5.1. Bleeding edge or not, it does exist, and all I am asking is that the PKGBUILD which uses it calls itself 8.5.1 and not 8.5.2. That is a completely separate issue from whether this should have been done at all. In most packages there are XXX and XXX-git. Since this is using a tag, and not simply git head, perhaps it should be called foldingathome-alpha or foldingathome-latest-tag.
Pinned Comments
SovietReimu1228 commented on 2024-08-22 14:48 (UTC)
I'll leave a note for those who are having trouble starting FAH after updating. You should do
pacman -Rs foldingathomeand install again. This will create thefah-clientuser.