Solved Why Subversion?

[ldgc]

Hi
I would like to know why subversion is the version control system of the base, doc and ports repositories.

Thanks in advance!

 

[obsigna]

Because it fits the job. So, why not?

 

[Cthulhux]

Because CVS is outdated.

 

[ldgc]

Because it fits the job.

What about other alternatives, e.g. GitHub?

 

[ldgc]

Because CVS is outdated.

I know that but thank you anyway

 

[obsigna]

GitHub is a platform which offers GIT and SVN as the VCS.

BTW, the FreeBSD sources are mirrored on GitHub and if you like, you can work with that one, instead of the SVN sources at freebsd.org.

https://github.com/freebsd/freebsd

 

[Cthulhux]

GitHub is anti-tech.

Exhibit A: https://www.mirbsd.org/permalinks/wlog-10_e20170301-tg.htm
Exhibit B: https://medium.com/karan/diversity-in-tech-conferences-and-electronconf-939751982c79

 

[ldgc]

GitHub is anti-tech.

Exhibit A: https://www.mirbsd.org/permalinks/wlog-10_e20170301-tg.htm
Exhibit B: https://medium.com/karan/diversity-in-tech-conferences-and-electronconf-939751982c79

Then why FreeBSD has the GitHub repository mentioned by obsigna?

 

[dclau]

Trending, perhaps?

 

[rigoletto@]

The FreeBSD GitHub mirrors are read-only. They probably are in there just because some people "live" in GitHub.

 

[phoenix]

Do a google search for something along the lines of "freebsd migrate cvs subversion" and you'll get the history of the migration, the reasoning behind it, and public debates around it, the upheaval that occurred, and the end result of using it. There's a lot of history and debate around this, that's all saved online.

Suffice to say that at the time of the migration, SVN suited the workflows best coming from a CVS background.

 

[dclau]

Or transparency, maybe. Don't quote me for that. A good thing, if you ask me.

 

[phoenix]

The FreeBSD GitHub mirrors are read-only. They probably are in there just because some people "live" in GitHub.

Pretty much. There's a SVN-to-GIT gateway so that those developers who prefer to use GIT can do so on their systems. Same for a SVN-to-Mercurial gateway (although I'm not sure if that one is still operational).

But, regardless of what you personally use to keep your patches, you'll need to submit a diff that SVN can understand, in order to get it into the official source repo.

 

[rigoletto@]

Or transparency, maybe. Don't quote me for that. A good thing, if you ask me.

Too late, I am already quoting you: https://svnweb.freebsd.org/

 

[ldgc]

Thank you all for your answers

 

[Snurg]

Just FYI, the topic is discussed in the exclusive developer circles, too. (I guess that is what phoenix meant - I found that link a few days ago when contemplating what to use myself)

 

[drhowarddrfine]

Think distributed control versus centralized control and you'll understand the difference between git and subversion.

 

[Datapanic]

ProTip:
#Note that devel/apr1 needs to have IPV6 disabled for svn+https to work

 

[SirDice]

https://wiki.freebsd.org/VCSWhy

 

[tobik@]

ProTip:
#Note that devel/apr1 needs to have IPV6 disabled for svn+https to work

Hmm, I have IPV6 enabled in devel/apr1 and svn+https works just fine.

 

[tingo]

And FWIW, if you don't like Github for any reason, there are alternatives, like Gitlab https://about.gitlab.com/

 

[CyberCr33p]

Is FreeBSD moving to git?

I read this:

FreeBSD Quarterly Status Report

The Core-initiated Git Transition Working Group met over the last quarter, however a report is still forthcoming. Discussions will continue in the fourth quarter of 2019. There are many issues to resolve including how to deal with contrib/, whether to re-generate hashes in the current Git repository, and how to best implement commit testing.

 

[Cthulhux]

Eww.