Menu

#62 Consider making a github repo for this?

Done
nobody
None
Medium
Enhancement
2022-01-04
2022-01-02
No

One thing I've been noticing is that due to the size of this repo, svn/sourceforge often fails checking out the entire repo at once via "svn checkout". This is a known problem with sourceforge/svn:
https://stackoverflow.com/questions/27267742/why-do-i-get-svn-e120106-ra-serf-the-server-sent-a-truncated-http-response-b

There's a few unsatisfying hacks to getting this to work (you basically have to re-run the checkout, clean and update it over and over again until it completes).

One question I have is whether you would be willing to either move this codebase to github or, alternatively, mirror the repo in both locations (sourceforge and github). Just a suggestion!

Discussion

  • Donald Robinson

    Donald Robinson - 2022-01-02

    I think that moving to GitHub is the plan that Ft. Collins is working toward. Maybe they could comment next week...

     
  • Mike VanDyck

    Mike VanDyck - 2022-01-04

    Only the trunk needs to be checked out in order to do builds. Checking out the entire repository includes all of the branches, each of which contains a copy of the files in trunk. I've updated the DownloadingSourceCode wiki to indicate that only the trunk should be checked out.

    There is a plan to eventually move to GitHub, as it has been identified as our corporate repository, but there are no immediate plans for when that will be started.

     
  • Mike VanDyck

    Mike VanDyck - 2022-01-04
    • status: New --> Done
     

Log in to post a comment.