Hi Sergei, > Today's "lastmidnight" script (which is a sh-script) is a bit lengthy > (such that it would better not be ported into perl). > It also makes use of SNV versioning. > Could you provide a comand-line clone of your vergen? With a short how-to?
the current version of vergen is checked in the project (tools/vergen). If you clone the git repository from SourceForge you will essentially get the same history as you'd have in a svn checkout. Now enter the trunk/ directory (or any directory below it) and run ../tools/vergen --format SVN_REVISION Currently it will print 1559 (without a newline). >From a git repository you will get the same output if you run ../tools/vergen --format GIT_REVISION Some caveats: computing the revision number is relative to a reference commit. I configured vergen to compute the number relative to the tag 'initial' which I set to the very first commit in the history (in fact we would have to tag the commit before the first one to get the correct number, but as this is not possible we simply increment the number we get from git. See the definition of the git-revision keyword in the .VERSION_DEFINITION file for some black magic. The artificial revision number this produces depends on the number of commits between the current head and the reference commit. It is identical to the svn revision number only for a clean "git-svn" branch. It will produce skewed results for derived branches with additional commits in between, but this is acceptable in my opinion. While we are at it, I have created a common Makefile include and some boilerplate templating code that can be used by all package build scripts. I also make use of this in the SuSE build. Have a look at trunk/package/common (run make in this directory and check the generated file 'demo' in order to learn how that works). > > 3. From my SF account I can not see tools for working with a > project-specific web site. If I understand correctly you can access the html document root of the hosted web directory from the shell account. I will try to set up a static HTML tree on the SF hosting site soon. > But main SF site is still very latent from my location. > > So, you say, that a project-specific web site (if set up at SF) will > work quickly from the rest of the world? It's quite snappy from here. > And main question: is it possible to upload nightly builds to this new > SF based site automatically? > > Does it have something like primitive ftp interface, in addition to some > profound http-based interactive upload features? SF has extended the shell service quite nicely. You can log in to move stuff around, and it is possible to scp/sftp to/from the SF project directory. No need for FTP or HTTP upload, I think. cu Martin ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
