Hi Mike, > What assistance will help with 'buildtool' conversion from cvs to git? > > http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/
For starters, somebody who knows something about git (if that person was also a perl hacker, even better. But the code should be commented well enough that it should be possible to write the new code even without a great deal of perl knowledge). As far as I can see, in order for buildtool to work against a repository that's not cvs based, we need the corresponding implementation of CvsExt.pm, CvsPserver.pm, ViewCVS.pm in http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/buildtool/DownloadTypes/ (most likely one implementation would be sufficient, since they all seem to be variations of the same thing) Once that's in place, the "cvs-sourceforge" server definition in http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/conf/sources.cfg?revision=HEAD needs to be updated accordingly. If we still want the packages to be stored in the SCM system, and we still want the packages page and changelog to be be (semi-)automatically generated, the script http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/tools/genpage.pl needs to be ported to work with the new SCM as well Just in case it's not obvious - I'm not volunteering for that job. To me, moving to a different SCM requires a lot of work, while not really solving a problem the project faces (IMHO) - unless I'm missing something, if all goes well and somebody spends the time on the migration and writing the new code for buildtool, we have pretty much the same we already have (the only difference would be the SCM being used). But of course, I'm not in a position to tell other people what they should or shouldn't do - I'm just trying to explain why I would have a hard time justifying spending my time on that (if I had that time at the moment). I may be able to help out with specific questions here and there, but at the moment, I don't have an awful lot of spare time on my hands. > This task is the main thing holding up a move to git. Just out of curiosity - what features of git make it the SCM of choice for leaf? Seriously, all I know about it is that it is used to store the sources of the linux kernel. Martin ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
