[PD-dev] moving to git

[Jonathan Wilkes]

As strongly and politely as I can advise: PLEASE don't pull until IOhannes implements SSL by default for these repos.
While it's wise to move away from Sourceforge, it's irresponsible to force a user in the year 2015 into an insecure connection in order to do so.
-Jonathan 


   

  On Wednesday, October 14, 2015 10:16 AM, IOhannes m zmoelnig <zmoelnig at iem.at> wrote:
   

 On 2015-07-30 11:05, IOhannes m zmoelnig wrote:
> ad #3
> i really would like to split that huge repository into small projects
> (mainly: per-library).
> i've already started working on this on [1], which is nothing much to
> show yet, but in the end it should document the process and provide a
> way to re-play the conversion.
> 

so i've done a first transition.

all the git-repositories can be found at

  http://git.puredata.info/cgit/svn2git/

they are browsable and can be cloned directly from the webpage.
however, these repos are meant as starting points, so we do not provide
*any write* access.
so once you forked, push to your own server (or gitlab, github,
sourceforge, you name it) and let us no.


the process is documented (a little bit) on [1], but some parts of the
migration had to be done manually (namely the selection of the paths to
base the various libraries on; and the merging/re-rooting of
repositories with independent branches).



so what is it?
===
an automated, history preserving, migration of the current svn directory
into multiple git repositories, one for each library.

# why should i use this?
if anybody who wants to start working on any of the pd-repo libraries
uses the same git repo as root, it is trivial to merge those changes
back together.
so using those repositories as starting point, should make collaboration
between independent devs a lot easier (compared to, when everybody does
their own conversion, or just starts off wherever they think).

# what is included?
i tried to capture as many libraries as possible (even those that had
been removed from the svn a while ago).
i tried to only include "libraries" (addons, plugins), regardless of
whether they are "abstractions", "externals", "scripts" or "gui-plugins".

# what is not included?
libraries that were only included via svn:externals (thus hosted on
different servers). this is mostly, Gem, gridflow and grrrr.
also some other libs that were not maintained on the svn but where only
added/removed a few times (without adding any real history): these
turned out to be too much of a hazzle for little value.

# externals vs abtractions
i did not discriminate between the two.
a few libraries were split on the two directories (e.g.
abstractions/footils and externals/footils) and i have taken the liberty
to re-combine them ("footils.git" contains both abstractions and externals)

# what is left to do?
svn2git migration wise, probably not too much.
however, i haven't really checked the resulting repositories (apart from
generic sanity), so there might be bugs in the migration script itself.


have fun.

gfamsdr
IOhannes


[1] https://github.com/umlaeute/pd-svn2git

_______________________________________________
Pd-dev mailing list
Pd-dev at lists.iem.at
http://lists.puredata.info/listinfo/pd-dev


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20151014/96abbcb3/attachment.html>