#17 Migrate and/or import CVS repository to GIT repositories

None
accepted
None
5
2013-05-29
2011-12-20
No

The new SourceForge Project interface supports multiple code repositories of different types as well as sub projects that can have their own code repositories of whatever type. Migrate and/or import the CVS repository to GIT repositories in the top level project or in sub projects (depending on the module) for each module, one time and/or ongoing, retaining all history.

Discussion

  • Robert James Clay

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1 @@
    -Amongst other reasons, the new SourceForge project will not be supporting CVS repositories \(at least, not anytime soon from what I understand\).    May have sub projects later that use GIT and/or other types of code repositories but for now, migrate the existing CVS repository to an SVN repository, retaining all history.
    +Amongst other reasons, the new SourceForge project will not be supporting CVS repositories \(at least, not anytime soon from what I understand\).  May have sub projects later that use GIT and/or other types of code repositories but for now, migrate the existing CVS repository to an SVN repository, retaining all history.
    
    • status: open --> accepted
    • assigned_to: Robert James Clay
    • Group: -->
     
  • Robert James Clay

    As it turned out; they were able to migrate the existing CVS repository:

    So there may be no particular reason to migrate the existing CVS code repository to an SVN repository, especially since it is so easy to migrate a particular 'module' in the CVS repository to its own GIT repository.

     
    • Stas Degteff

      Stas Degteff - 2013-05-09

      Division into modules isn't best idea IMHO. Now can simple checkout full project code using one command and next compile all required libraries and programs. If each module will stored in own repository, this way will be don't allowed.

       
      Last edit: Stas Degteff 2013-05-09
  • Robert James Clay

    • summary: Migrate CVS repository to an SVN repository --> Migrate and/or import CVS repository to GIT repositories
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1 @@
    -Amongst other reasons, the new SourceForge project will not be supporting CVS repositories \(at least, not anytime soon from what I understand\).  May have sub projects later that use GIT and/or other types of code repositories but for now, migrate the existing CVS repository to an SVN repository, retaining all history.
    +The new SourceForge Project interface supports multiple code repositories of different types as well as sub projects that can have their own code repositories of whatever type. Migrate and/or import the CVS repository to GIT repositories in the top level project or in sub projects (depending on the module) for each module, one time and/or ongoing, retaining all history.
    
     
  • Robert James Clay

    It's true that one can "checkout full project code using one command and next compile all required libraries and programs" but in the case of, for instance, packaging for Debian/Ubuntu it's not all that useful. For one thing, it pulls in modules that are not being worked on. For another; Debian packaging is (and should be) tracked separately; that could perhaps be tracked in a separate branch in the cvs repository but I primarily use GIT these days and so will be using that.

     
  • Robert James Clay

    Keep in mind that the version number for a (non-native type) Debian package consists of both the version of whatever is being packaged plus a version number for the packaging, separated by dash. The existing debian directories in the CVS repository for the modules does that but does not take into account the packaging changes that may need to be done; again, that could perhaps be done in cvs branches but after primarily using GIT for development work I find that to be awkward at best.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks