• waiglEnglish
    arrow-up
    14
    arrow-down
    0
    ·
    2 months ago
    link
    fedilink

    Is OpenBSD seriously still using CVS for development?

    • go $fsck yourselfEnglish
      arrow-up
      16
      arrow-down
      1
      ·
      2 months ago
      link
      fedilink

      Yeah, that’s weird. It’s pretty unorthodox to use a pharmacy chain for development.

      • sugar_in_your_teaEnglish
        arrow-up
        5
        arrow-down
        0
        ·
        2 months ago
        link
        fedilink

        To be fair, they have a pufferfish as a mascot, so there’s bound to be some need for pharmaceuticals.

    • rhabarbaOPEnglish
      arrow-up
      7
      arrow-down
      3
      ·
      2 months ago
      link
      fedilink

      Yes, it is, because it does the job. Why exactly shouldn’t they?

      • chellomereEnglish
        arrow-up
        3
        arrow-down
        0
        ·
        2 months ago
        link
        fedilink

        For example, maybe branching is something you’d like to be able to do without it being a nightmare?

        • rhabarbaOPEnglish
          arrow-up
          9
          arrow-down
          0
          ·
          2 months ago
          link
          fedilink

          OpenBSD seems to be able to have branches (CURRENT and STABLE), and they seem to be able to manage them just fine.

    • FredEnglish
      arrow-up
      4
      arrow-down
      0
      ·
      2 months ago
      edit-2
      2 months ago
      link
      fedilink

      CVS is the authoritative repository of code, and they recommend to users to use that or reposync (built atop of CVS) to keep their system updated.

      There is also a GitHub mirror , and got is an OpenBSD project, and I suspect a number of devs use one of those for local work until it’s time to push the changes to the authoritative tree.

    • Jagger2097English
      arrow-up
      4
      arrow-down
      0
      ·
      2 months ago
      link
      fedilink

      They can work on replacing that next