Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [e4-dev] Using cvs import in therepository/CommonBuildInfrastructure


*If* we decide to stick with Git, the natural way to handle it would be to write a Git-aware plugin for PDE/Build. This should be very easy. A plugin for SVN exists and only contains 1 small Java file (see [1]). It produces an Ant script that employs <svn> ant command. I don't know if there are any native ant commands for Git, but via can get away with <exec>, see [2].



As a temporary measure, looking at what PDE/Build does when fetching from CVS, it seems that git-cvsserver should be enough for it. The only thing is that you'll have to change maps to specify branch-relative path, and it would not be possible to build from tag unless you create a branch from that tag.

But, this all assumes we have already decided on Git, which we have not. So maybe we should actually go forward with your suggestion.

(I have realized that it might not be that hard to combine the history of e3 and e4 after the fact, even if cvsps produces incompatible history from e3 and e4 repositories. And it *will* actually produce incompatible history, given that you are only copying a subset of plugins into e4 CVS repository as far as I understand. Still, with a certain amount of Git-fu this can be handled.)

2008/11/13 Oberhuber, Martin <Martin.Oberhuber@xxxxxxxxxxxxx>
Do you have other suggestions?
CVS Repository e35 is a given.
Repository e4 is more free to choose, but must
be synchronized against its ancestor (e35)
frequently, and should look like a CVS repository
to the build infrastructure...
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member

From: e4-dev-bounces@xxxxxxxxxxx [mailto:e4-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrey Tarantsov
Sent: Wednesday, November 12, 2008 8:38 PM

To: E4 Project developer mailing list
Subject: Re: [e4-dev] Using cvs import in therepository/CommonBuildInfrastructure

1.) git cvsimport e35-cvs -->  e35-git
2.) git cvsimport e4-cvs  -->  e4-git
3.) git init e4-merged-git
   git pull e35-git --> e4-merged-git
   git pull e4-git  --> e4-merged-git

Took a few moments to figure what you mean, rather unusual. But yes, should be possible. (Still, for me it sounds very brave. :)


e4-dev mailing list


Back to the top