There are multiple permissively licensed git implementations, including game of trees (which is slated to replace cvs for openbsd), and git9 (by @orib, admittedly probably not easily portable outside of plan9.
Since the format itself is not GPL’d, and the base system doesn’t need to ship with a git client, I expect it’s not considered a huge problem; and once game of trees is released it can be the officially-sanctioned client.
One of the goals of OpenBSD is that it’s “free” as in “free to do whatever you want with it”. This is a different definition of “free” as used it the GPL. There’s nothing wrong with the GPL definition as such, but having GPL in the base system removes the OpenBSD definition of “free”, and I don’t think caring about that is either “childish” nor “cringe-worthy”.
I used to run a really big CVS server, and while CVS is a huge PITA to use, I pretty much had the entire source memorized, and it was very simple to administer at a scale where a git repo would melt down in a puddle of goo.
agreed, but that’s not necessarily the workflow of a committer, just a contributor.
I don’t mind CVS for the basic use cases of keeping track of a few files here and there. Maintenance of CVS is an entirely different thing however, especially in a distributed scenario.
Why is FreeBSD moving from an Apache licensed project to a GPL licensed one?
There are multiple permissively licensed git implementations, including game of trees (which is slated to replace cvs for openbsd), and git9 (by @orib, admittedly probably not easily portable outside of plan9.
Since the format itself is not GPL’d, and the base system doesn’t need to ship with a git client, I expect it’s not considered a huge problem; and once game of trees is released it can be the officially-sanctioned client.
As far as I know OpenBSD has no official plans to switch away from CVS.
Am I the only one who thinks that this GPL-aversion is incredibly childish and cringe-worthy?
Projects can be good community neighbors or bad community neighbors, and in terms of free software, they are certainly poor neighbors.
One of the goals of OpenBSD is that it’s “free” as in “free to do whatever you want with it”. This is a different definition of “free” as used it the GPL. There’s nothing wrong with the GPL definition as such, but having GPL in the base system removes the OpenBSD definition of “free”, and I don’t think caring about that is either “childish” nor “cringe-worthy”.
[Comment from banned user removed]
lolwut? I don’t know if I should upvote this as it’s hilarious, or downvote as troll.
From my perspective as a non-US-person, these groups feel pretty close in their regressive mindset and the corporate worshiping.
That’s why I was curious.
If you consider OpenBSD an act of corporate worship, you have an unusual way of thinking. I struggle to see the similarity.
Yes, I do.
There’s a good discussion of the reasoning here.
Subversion? When did they move off of CVS?
In 2008-2012:
Ugh. Time flies when you’re old… :(
Can still use OpenBSD if you’re nostalgic about forgetting
-P
incvs co
or having your binary files mangled by forgetting to mark them as such 🙃I used to run a really big CVS server, and while CVS is a huge PITA to use, I pretty much had the entire source memorized, and it was very simple to administer at a scale where a git repo would melt down in a puddle of goo.
OpenBSD offers a copy in git, so unless you are an OpenBSD committer, chances are you never have to actually play in cvs land… thankfully :)
cvs up; cvs diff; send patch per mail; isn’t really that bad.
agreed, but that’s not necessarily the workflow of a committer, just a contributor.
I don’t mind CVS for the basic use cases of keeping track of a few files here and there. Maintenance of CVS is an entirely different thing however, especially in a distributed scenario.
We still use Visual SourceSafe at work. The binary is 20+ years old and is distributed from a network share.
I’m a bit surprised that it is this close to the holidays, but then it seems like it’s not a production-breaking change as the old repos stay up.
https://svnweb.freebsd.org/base?view=revision&revision=368820