summaryrefslogtreecommitdiff
path: root/solenv
diff options
context:
space:
mode:
authorTor Lillqvist <tlillqvist@suse.com>2011-09-21 12:49:33 +0300
committerTor Lillqvist <tlillqvist@suse.com>2011-09-21 12:49:33 +0300
commit164456eab5c8542b9ce87c5ccd44db902c1214a1 (patch)
tree5bf49447a7521ac1f66c966f204a30267db1dc4c /solenv
parent94f6a72f7ade62a146a1e1254cc0a4638d48efc5 (diff)
Update to match reality
But actually, I would really love it if we could get rid of this version.lst file. Surely we can put this information, if it has to be hardcoded somewhere, in the same minor.mk that already contains version information (and which, unlike this file, actually has been kept updated by us). Or alternatively, get rid of minor.mk and use just this file. Best of all would be to just use the version number from the AC_INIT in configure.in, wouldn't it? Isn't that the normal thing to do? Also, I don't see what hardoced version timestamps as in this file are useful for. If such a timestamp corresponds one-to-one with a version number, the information clearly is redundant? A *build* timestamp is another thing, that might be more useful if file timestamps or package timestamps don't give enough information.
Diffstat (limited to 'solenv')
-rwxr-xr-xsolenv/inc/version.lst8
1 files changed, 4 insertions, 4 deletions
diff --git a/solenv/inc/version.lst b/solenv/inc/version.lst
index 200cdf53e924..aed0b5ae68ed 100755
--- a/solenv/inc/version.lst
+++ b/solenv/inc/version.lst
@@ -26,9 +26,9 @@
#*************************************************************************
OOOBASEVERSIONMAJOR=3
-OOOBASEVERSIONMINOR=4
+OOOBASEVERSIONMINOR=5
OOOBASEVERSIONMICRO=0
-OOOBASEVERSIONDAY=1
-OOOBASEVERSIONMONTH=10
-OOOBASEVERSIONYEAR=2010
+OOOBASEVERSIONDAY=21
+OOOBASEVERSIONMONTH=9
+OOOBASEVERSIONYEAR=2011