Hi Sergei, My apologies for the confusing situation with Git. The exact path for moving from SVN to Git wasn't clear at first, but I think the dust is starting to settle.
This may seem like overkill in comparison to how we used SVN, but it does add some considerable flexibility. The development work in the Frankfurt team is driven by customer requirements from various projects. Using Git allows us to easily "context switch" between different coding tasks and will help us move code back upstream to the open source project. Basically, the "authoritative" repository is on GitHub [https://github.com/openxpki/openxpki]. The additional user repositories you see on GitHub are forked from this main repository and allow the users to publish their work without making the commits an "official" part of the project. A developer that does not have write permissions for the main repository can submit a "pull request" back to the project. Within the main repository, there are currently two branches: master and develop. The idea here is that the master branch shall represent a stable condition while new work is first added to the develop branch where it is reviewed and tested. As a CVS and Subversion veteran, I must admit that I spent my first week or so in the project with Martin complaining about how complicated Git was. He was also doing some extra "branching fu" to track the differences between the configurations for dev, test and prod systems. At some point, however, it "clicked" and I've become an avid Git user. In addition to having Martin around to explain some of Git, there were two things that were very helpful in my learning process: the Version Control With Git book from O'Reilly and a Git GUI that displays the commits and branches in a tree diagram (I'm using GitX on my Mac, but there are a few interesting alternatives for other OSs). The GUI is really helpful for viewing what is happening in all these branches. Best regards, Scott On Mar 20, 2012, at 22:51 , Sergei Vyshenski wrote: > On 21.03.2012 0:08, Oliver Welter wrote: >> On 20.03.2012 20:11, Sergei Vyshenski wrote: >>> Just take a tarballs from >>> >>> http://www7.openxpki.org/lastmidnight/index.html >>> >>> and install it in a plain UNIX way. >>> >>> This should allow submitting utf-8 names in request, >>> visualizing utf-8 names from database, issuing certs with utf-8 names etc. >> > >> from what sources are those tarballs? I use the latest dev code from git >> and this is NOT working. > > 1. I am already totally lost with "dev" or whatever branches of various > openxpki git repositories scattered over the Internet. > Those tarballs are built from such a git snapshot, that the output of > "git log -1" gives: > > commit 2b70092617d580e887b65d40a378616ba25771db > Author: djulia <djulia@95d9436f-6502-0410-902c-bd9569d1a17e> > Date: Fri Feb 24 20:26:49 2012 +0000 > > perl-5.14 patch > Example of how to follow new syntax requirements. > Works in older perls too. > > git-svn-id: > https://openxpki.svn.sourceforge.net/svnroot/openxpki@1591 > 95d9436f-6502-0410-902c-bd9569d1a17e > > Also, inside this snapshot: > > openxpki/.git> cat config > > gives: > > [core] > repositoryformatversion = 0 > filemode = true > bare = false > logallrefupdates = true > [remote "origin"] > fetch = +refs/heads/*:refs/remotes/origin/* > url = git://openxpki.git.sourceforge.net/gitroot/openxpki/openxpki > [branch "master"] > remote = origin > merge = refs/heads/master > > > 2. "Not working" is not a description of a problem. Here it works ok > with various perls as reported in my message, which introduced the > patch. Tested it on empty host, installed from scratch. Either you are > lost with various gits too, or you are introducing something wrong > during preparation of specific type of lynux distribution. > > Maybe a reasonable starting point for you is just to try the specified > (universal unix) tarbals, which I claim to be working ones? > > Regards, Sergei > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > OpenXPKI-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openxpki-devel -- Scott T. Hardin <[email protected]> Hard 'n Software Consulting GmbH An der Schaeferbuche 4-6 35039 Marburg Germany Phone: +49 6421 18 36 36 Mobile: +49 178 21 21 703 Internet: http://www.hnsc.de Handelsregister: 16 HRB 2232, Amtsgericht Marburg Geschaeftsfuehrer: Scott T. Hardin ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
