Current status: I guess it's time to keep local (Git) repository copies of FreeBSD and OpenBSD src, since I keep looking at them frequently enough.
(I know, Git isn't the native VCS format for either, but Git is a lot easier to work with and this is for investigating things, not building or working on them.)
Joshua M. Clulow
in reply to Chris Siebenmann • • •Chris Siebenmann
in reply to Joshua M. Clulow • • •Joshua M. Clulow
in reply to Chris Siebenmann • • •silverwizard
in reply to Joshua M. Clulow • •Haelwenn /элвэн/
in reply to Joshua M. Clulow • • •Well given 9front managed to do a git rewrite and switch to it (they used mercurial before) there's at least precedent in doing so.
With 9front probably not having the option of using upstream git, while OpenBSD seems mostly concerned about infra maintainability (and security).
Joshua M. Clulow
in reply to Haelwenn /элвэн/ • • •Haelwenn /элвэн/
in reply to Joshua M. Clulow • • •cow
in reply to Haelwenn /элвэн/ • • •It kinda is licensing as OpenBSD is trying to remove GPL software. (quoted from openbsd.org/policy.html)
The GNU Public License and licenses modeled on it impose the restriction that source code must be distributed or made available for all works that are derivatives of the GNU copyrighted code.
While this may superficially look like a noble strategy, it is a condition that is typically unacceptable for commercial use of software. So in practice, it usually ends up hindering free sharing and reuse of code and ideas rather than encouraging it. As a consequence, no additional software bound by the GPL terms will be considered for inclusion into the OpenBSD base system.
For historical reasons, the OpenBSD base system still includes the following GPL-licensed components: the GNU compiler collection (GCC) with supporting binutils and libraries, GNU CVS, GNU texinfo, the mkhybrid file system creation tool, and the readline library. Replacement by equivalent, more freely licensed tools is a long-term desideratum.
OpenBSD: Copyright Policy
www.openbsd.orgHaelwenn /элвэн/
in reply to cow • • •And even was there in 1997 when that document got created so not a reaction to GPLv3 (which I would have expected to create this kind of policy given the mess it created): cvsweb.openbsd.org/www/policy.…
luca
in reply to Chris Siebenmann • • •Chris Siebenmann
in reply to luca • • •@luca And today I learned that FreeBSD has switched to Git from SVN (I think, based on how they list the Git repo first on their list). I am behind the (FreeBSD) times.
(I cloned the github version of their repo because that's what I'd had in my mind as the Git version of FreeBSD.)
Norman Wilson
in reply to Chris Siebenmann • • •I'd settle just for an unpacked copy of the tarballs. Or do you want to track changes?
Shouldn't be too hard to automate.
Chris Siebenmann
in reply to Norman Wilson • • •Chris Siebenmann
in reply to Chris Siebenmann • • •Since I last paid attention, FreeBSD has moved its official source to a (self-hosted) Git repository, so I can clone and pull directly from their master version.
I'm currently resisting the temptation to keep a local copy of NetBSD source. I almost never look at it (sorry, NetBSD, you're the extra BSD), and NetBSD's official version seems to still be in CVS, although they have an official Github-hosted Git mirror.