> OpenBSD source code is also available but it uses CSV and I am not sure it includes the source code for all CLI tools.
Isn't that pretty much the whole point of BSD distributions? And IIRC OpenBSD doesn't even allow binary drivers, everything distributed as part of OpenBSD which runs on the host CPU is open-source (OpenBSD does bundle firmwares blobs)
(otoh it is nice to get more OS support in psutil, it's a neat piece of kit though with an annoying history of API changes)
Ya I'm not really sure what they were getting at there. Is it that they think the OpenBSD source layout is hard to understand, they saw cvs and stopped looking or is it that they believe OpenBSD ships with tools that do not have the source released?
> Is it that they think the OpenBSD source layout is hard to understand
OpenBSD's source tree layout is almost the same as FreeBSD's.
In both trees the source for the various CLI tools lives in src/bin/, src/sbin/, src/usr.bin/, src/usr.sbin/, and a similar structure in src/gnu/ (eg. src/gnu/usr.bin/)
I don't mean anything, the chevron means it's a direct quote from TFA (most likely just a typo which nobody else caught because everybody read it at "CVS" in context, I sure did)
Nothing directly to do with psutil, but related to cross-platform handling of differences between Linux, and various * BSDs (also, a reminder that while vendoring dependencies a la "best practice" go, it's good to keep an eye on upstream - or risk missing fixes).
9 comments
[ 3.3 ms ] story [ 33.2 ms ] threadIsn't that pretty much the whole point of BSD distributions? And IIRC OpenBSD doesn't even allow binary drivers, everything distributed as part of OpenBSD which runs on the host CPU is open-source (OpenBSD does bundle firmwares blobs)
(otoh it is nice to get more OS support in psutil, it's a neat piece of kit though with an annoying history of API changes)
OpenBSD's source tree layout is almost the same as FreeBSD's.
In both trees the source for the various CLI tools lives in src/bin/, src/sbin/, src/usr.bin/, src/usr.sbin/, and a similar structure in src/gnu/ (eg. src/gnu/usr.bin/)
https://svnweb.freebsd.org/base/head/
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/
http://www.openbsd.org/papers/anoncvs-paper.pdf
http://www.openbsd.org/papers/anoncvs-slides.pdf
I was puzzled by the line above regarding source. Like most (all?) BSDs the system is easily checked out and built:
http://www.openbsd.org/anoncvs.html
or, basically:
# cd /usr
# cvs -qd anoncvs@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_5_8 -P src
# cd /sys/arch/amd64/conf
# config GENERIC.MP
# cd ../compile/GENERIC.MP
# make depend bsd install
# cd /usr/src
# make obj build
# reboot
Nothing directly to do with psutil, but related to cross-platform handling of differences between Linux, and various * BSDs (also, a reminder that while vendoring dependencies a la "best practice" go, it's good to keep an eye on upstream - or risk missing fixes).