Re: [dev] Important Process for Mercurial Users
Hi Bernd, On Friday 31 July 2009, Bernd Eilers wrote: Everyone using a mercurial based CWS MUST enter the new milestone in EIS manually after rebasing the CWS to a new milestone using mercurial commandline or gui tools. Cannot this be automated? With git, all you'd need is to have a post-update hook on the server that does 'git describe' (finds the most recent tag that is reachable from a commit) on the CWS, and just gives the tag to the EIS. I suppose the same must be achievable with Mercurial, right? Regards, Kendy - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Would like to participate
Hi, I am an Egyptian software developer living in London, I started my career by working 2 years as teacher in the university, and by 2008 I decided to go to work in the field. I am working with Java technologies. I would like to participate in an open source project to learn more, meet new people, and do something useful in my free time. Can you help me in that? Many thanks. -- Mina Daoud IT Developer
Re: [dev] Important Process for Mercurial Users
Hi Jan, Jan Holesovsky wrote: Hi Heiner, On Wednesday 26 August 2009, Jens-Heiner Rechtien wrote: Everyone using a mercurial based CWS MUST enter the new milestone in EIS manually after rebasing the CWS to a new milestone using mercurial commandline or gui tools. Cannot this be automated? With git, all you'd need is to have a post-update hook on the server that does 'git describe' (finds the most recent tag that is reachable from a commit) on the CWS, and just gives the tag to the EIS. I suppose the same must be achievable with Mercurial, right? Yes, something like that is possible with hg. Great! But it's somewhat wrong also because in most cases it's more relevant what's in your local working repository and that might be much more current than what you have in the outgoing rep. I don't think it is wrong. In your local repository, you don't care about the milestone at all, it is important for the outside world only. From the other mail: - 8 - Thus in order to not break processes which depend on the correct milestone version information in EIS like buildbots or automated tests do for example a developer MUST update milestone information in EIS manually after using mercurial tools to update the source code to the new milestone. - 8 - The buildbots and the automated tests will never get what you have locally, unless you push that. So from my understanding, the information in the EIS should track what is published (pushed) = post-update hook is what we want. So the whole notion of the current milestone is somewhat unclear in a DSCM scenario. No, the notion of the current milestone is perfectly defined - the most recent tag that is reachable from the commit. What is somewhat unclear in the DSCM scenario is the definition of Child workspace :-) - is the CWS what is on the server, or each and every clone out there? Is every clone the one CWS, or is it several CWSes? ;-) Heretic idea comes to my mind - what about to discard the 'current milestone' info from EIS completely, and update buildbots/automated tests/etc. to count the 'current milestone' themselves using the Mercurial equivalent of 'git describe'? Then we never can be wrong, and the info can never be outdated/out of sync. Haven't thought finally about it. There will be at least a command line method to update the milestone. The rebasing using the Mercurial tools only is a great leap ahead [thanks for that!], let's not make a step back by introducing commands that are not really necessary... I'll keep that in mind. Some great suggestions here, I'll have a look at them! Regards, Heiner - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Moving to bost 1.3?
Hi, overlooked this ... On Wednesday, 2009-08-19 10:20:18 +0200, Rene Engelhard wrote: On Wed, Aug 19, 2009 at 08:56:23AM +0200, Regina Henschel wrote: The new Math libraries 'Special Functions' and 'Statistical Distribution' are not included in Boost 1.34, but first in Boost 1.35. The accuracy of those functions is ongoing work in Calc and doing it ourself has been a lot of work. Please talk with Eike about the need for that libraries. Though that also would result in linkage against the actual lib while we so far only used boost headers. Nothing bad per se, but it should be kept in mind (and the boost module needs to be changed to actually build boost :-)) This indeed might be an obstacle.. hopefully things changed since I last tried years ago, getting that Jam build stuff to run on all major platforms was horrible back then, and didn't ... However, having the boost math lib would be of great benefit for Calc, so I strongly vote for possibly the latest version of boost that's available, but at least 1.35 Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 D412 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the e...@sun.com account, which I use for mailing lists only and don't read from outside Sun. Use er...@sun.com Thanks. pgpkxynoxZ78C.pgp Description: PGP signature
Re: [dev] How to update l10n and rebuild?
Hi Kristján, On Friday, 2009-08-21 11:30:57 +, Kristján Bjarni Guðmundsson wrote: I am building OO in cygwin with DEV300_m54, which works fine. However I am having problems updating the build after I have changed a few strings in the l10n module. The problem is that building again doesn't pick up the new strings without doing a dmake clean and a complete build. I have tried deleting the output directories from l10n and instsetoo_native however nothing like that works. How did you rebuild after having removed output from the l10n module? cd instsetoo_native build --all respectively a dmake in OOo's root dir did not work? Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 D412 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the e...@sun.com account, which I use for mailing lists only and don't read from outside Sun. Use er...@sun.com Thanks. pgp6Yjo5z166t.pgp Description: PGP signature
Re: [dev] Moving to bost 1.3?
Hi Eike, However, having the boost math lib would be of great benefit for Calc, so I strongly vote for possibly the latest version of boost that's available, but at least 1.35 I didn't hear any strong objections against using 1.39 (or 1.38 at least for system-boost), so I think I'll go for that. I'll leave the task of building boost and linking against it for you, for a follow-up CWS :) Ciao Frank -- - Frank Schönheit, Software Engineer frank.schoenh...@sun.com - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Important Process for Mercurial Users
Jens-Heiner Rechtien wrote: Hi Jan, Jan Holesovsky wrote: Hi Bernd, On Friday 31 July 2009, Bernd Eilers wrote: Everyone using a mercurial based CWS MUST enter the new milestone in EIS manually after rebasing the CWS to a new milestone using mercurial commandline or gui tools. Cannot this be automated? With git, all you'd need is to have a post-update hook on the server that does 'git describe' (finds the most recent tag that is reachable from a commit) on the CWS, and just gives the tag to the EIS. I suppose the same must be achievable with Mercurial, right? Yes, something like that is possible with hg. But it's somewhat wrong also because in most cases it's more relevant what's in your local working repository and that might be much more current than what you have in the outgoing rep. So the whole notion of the current milestone is somewhat unclear in a DSCM scenario. Haven't thought finally about it. There will be at least a command line method to update the milestone. what about this: tho code basis itself knows about it's milestone, it's in solenv/inc/minor.mk, so EIS should be able to grab that information from the hg repository directly. Martin Regards, Heiner - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
