I'm trying to get S@H built, and maybe even packaged for NetBSD's pkgsrc. I finally got BOINC built so I think I can proceed.

I see how to pull the latest S@H version from SVN, but is there a way to pull a specific version? And is there documentation on what SVN tag/release/etc corresponds to "released" seti@home versions? If I'm going to package it, I'll want to grab a specific one so that it doesn't break more often as needed as SVN "latest" continues to change.

Thanks!

---

Ah-ha, I found this little gem in another Q&A:

svn checkout https://setisvn.ssl.berkeley.edu/svn/seti_boinc@3304 seti_boinc

Now I just need to figure out what versions are golden. For example, My PC has currently got v8 8.08, but I don't know how to map that to an SVN revision.

---

I'm fairly certain the SVN repository is deprecated. The current repository for BOINC is at Github.
https://github.com/BOINC/boinc

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

He's not looking for BOINC, but for the source code for Seti. Which is at SVN.

---

He's not looking for BOINC, but for the source code for Seti. Which is at SVN.

Ohh, never mind.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

It beats me how CM is being done on this. Here's what I see.
The seti@home version, as reported in the client, appears to be set by the configure.ac file.

https://setisvn.ssl.berkeley.edu/svn/seti_boinc/ - setiathome_v8, 8.00

I guess if you want to use a branch, you know it already; there's little explanation about them.
The only recent looking branch is:
sah_v7_opt/AKv8 - setiathome_v8, 8.22

Meanwhile as a cruncher, I'm running 8.08 on CPU, and 8.20 on opencl_intel, and 8.22 opencl_nvidia.

So I get the feeling that the "main" branch is not being used for the currently distributed clients. Still, without some further explanation, I'll stick with that one.
I'll just hope the current revision 3997 is workable.

---

There are two main sets of application, each relating to a type of data (AstroPulse and MultiBeam).
Each application "family" has its own version control, and is under control of its author.
There are families for various combinations of processor type (CPU, GPU maker, operating system) the key thing is they all branch from the parent 8.0 for MultiBeam and (confusingly) 7. for AstroPulse.
The parent defines the set of algorithms to be applied and is used to "calibrate" the results from the individual applications.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Thanks for the explanation. That helps.

---