Hi Maho, Am 01.12.08 12:39, Maho NAKATA schrieb: > I was thinking this while go home. I think it is purly my problem :) > I'd like to ask you to check minor.mk which will be placed at root > dir of my checkout from solenv/inc/minor.mk to get the tag infomation.
> a. we need to check which tag the testautomation archive comes from. > b. on CVS checkout or svn checkout, we can check immdeately > c. .svn dir is too large and I don't provide ".svn" data. <-root of the > problem > d. for OOO300, this is CVS, I leave CVS dir untouched. > e. for DEV300, this is SVN, I remove .svn dir. > f. so I should include solenv/inc/minor.mk in my checkout. > > I think - there may be better ideas, of course, I also appriciate > for your idea... My decent idea is to create a file like an ini-file in directory /testautomation/global/version.txt I think you don't have to play around with those files from CVS or SVN as you know what version you are getting while checkout. There is already a simple (not yet used or finished) version check prepared in testautomation/global/master.inc on line 138 (SVN version OOO300m36) that says. Use a control file /testautomation/global/version.txt. It looks like an ini-file Create it like this: [EnvironmentVersion] Current=OOO300 DisplayName=3.0.1 Minor=m36 Thats it for now :-) Maybe we can automate this process in the future directly during the build process but currently it is not possible. Best Regards Helge -- =============================================================== Sun Microsystems GmbH Helge Delfs Nagelsweg 55 Quality Assurance Engineer 20097 Hamburg OOo Team Lead Automation http://qa.openoffice.org mailto:[EMAIL PROTECTED] http://wiki.services.openoffice.org/wiki/User:Hde --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
