Conversation

Notices

1. Embed this notice
   Chris Siebenmann (cks@mastodon.social)'s status on Thursday, 07-Nov-2024 04:31:46 JST Chris Siebenmann

   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.)

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Joshua M. Clulow (jmc@m.unix.house)'s status on Thursday, 07-Nov-2024 04:32:22 JST Joshua M. Clulow

     in reply to

     @cks Yeah I think given they have to rewrite git before they can use it, it might be a while before they switch haha

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Joshua M. Clulow (jmc@m.unix.house)'s status on Thursday, 07-Nov-2024 04:32:23 JST Joshua M. Clulow

     in reply to

     @cks I thought FreeBSD moved to git a few years ago

   • Embed this notice
     Chris Siebenmann (cks@mastodon.social)'s status on Thursday, 07-Nov-2024 04:32:23 JST Chris Siebenmann

     in reply to

     • Joshua M. Clulow

     @jmc It turns out it did and I was just behind the times in my assumptions. (I went to their Github mirror, which is now a true mirror instead of a SVN to Git conversion the way OpenBSD I think still is.)

   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Thursday, 07-Nov-2024 04:37:30 JST silverwizard

     in reply to

     • Joshua M. Clulow
     @jmc @cks They're on it gameoftrees.org/
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 07-Nov-2024 04:38:08 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Joshua M. Clulow
     @jmc @cks 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).
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 07-Nov-2024 04:48:27 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Joshua M. Clulow
     @jmc @cks I don't think it's licensing, git is under GPLv2 though so same as gcc 4.2.1 (last version before GPLv3 relicensing) which is in OpenBSD's base along few other GNU software: https://cvsweb.openbsd.org/src/gnu/gcc/
   • Embed this notice
     Joshua M. Clulow (jmc@m.unix.house)'s status on Thursday, 07-Nov-2024 04:48:29 JST Joshua M. Clulow

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan @cks I think 9front probably tolerates a lot more risk (and has a lot less critical deployments) than OpenBSD. I also received the perception that OpenBSD really only care specifically about having no software required to work on the OS shipped from outside their base repository, and they have a pretty firm policy on what licences can be used in there; hence, their work in progress Game Of Trees git reimplementation.

   • Embed this notice
     cow (cow@social.cowingtonpost.com)'s status on Thursday, 07-Nov-2024 05:16:27 JST cow

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • Joshua M. Clulow
     @lanodan @jmc @cks It kinda is licensing as OpenBSD is trying to remove GPL software. (quoted from https://www.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.
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 07-Nov-2024 05:25:53 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Joshua M. Clulow
     • cow
     @cow @jmc @cks Oh, TIL!
     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): https://cvsweb.openbsd.org/www/policy.html?rev=1.1&content-type=text/x-cvsweb-markup
   • Embed this notice
     Chris Siebenmann (cks@mastodon.social)'s status on Thursday, 07-Nov-2024 12:58:28 JST Chris Siebenmann

     in reply to

     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.

     Haelwenn /элвэн/ :triskell: likes this.