On 1/12/12 8:40 PM, Ariel Constenla-Haile wrote:
Hi Jürgen,
On Thu, Jan 12, 2012 at 12:29:50PM +0100, Jürgen Schmidt wrote:
3. Values in minor.mk
The main/solenv/inc/minor.mk contains several values that have
influence on several places.
For example the name of the download files, the content of the About
dialog, etc.
The value are current:
RSCVERSION=340
RSCREVISION=340m1(Build:9584)
BUILD=9584
LAST_MINOR=m1
SOURCEVERSION=OOO340
I think we should define new values and the question is how we want
to use this values.
I would propose the following for the short term:
RSCVERSION=340 -> we keep this for now because are working on an AOO
3.4 and we will change it when we work on 4.0 or 3.4.1 accordingly
RSCREVISION=340m1(Build:9584) -> here i am not sure how we should
handle this. We have currently no similar build process that we had
in the past. I would propose a value like "340 (Rev.: r1230461)"
where we change the revision number dynamically.
BUILD -> don't have a good idea yet
LAST_MINOR -> the same, I haven't a good idea yet.
I've been working on this http://s.apache.org/X2B
and in the meantime found a solution, I'll post something on the
weekend.
great, to good to hear that. What do you think about the dynamical
update of the revision number during the build? Or maybe a special
script that can be triggered after an update.
I know you get the revision number during the configure switch but I
think about an update without configure. For a minor update of only a
few files i would simply rebuild without configure.
Juergen
