Commit b734be7a authored by panne's avatar panne
Browse files

[project @ 2004-09-19 09:41:29 by panne]

Use version info from configure.ac
parent f271c1f8
The Glasgow Haskell Compiler, version 6.3
The @PACKAGE_NAME@, version @PACKAGE_VERSION@
......@@ -2,10 +2,17 @@
AC_INIT([Glasgow Haskell Compiler], [6.3], [glasgow-haskell-bugs@haskell.org], [ghc])
AC_CONFIG_SRCDIR([ghc.spec.in])
# Compute the version number and the release, they are needed by the .spec file.
AC_SUBST([version], [[`sed 's/.* version \([0-9][0-9.]*\).*/\1/' VERSION`]])
# Calculate project version as an integer, using 2 digits for minor version
case $PACKAGE_VERSION in
*.?) ProjectVersionInt=`echo "$PACKAGE_VERSION" | sed 's,^\(.*\)\.\(.\)$,\10\2,'` ;;
*.??) ProjectVersionInt=`echo "$PACKAGE_VERSION" | sed 's,^\(.*\)\.\(..\)$,\1\2,'` ;;
*) AC_MSG_ERROR([bad package version $PACKAGE_VERSION]) ;;
esac
AC_SUBST([ProjectVersionInt])
# Hmmm, we fix the RPM release number to 1 here... Is this convenient?
AC_SUBST([release], [1])
# Write the results...
AC_CONFIG_FILES([ghc.spec])
AC_CONFIG_FILES([ghc.spec VERSION docs/users_guide/ug-book.xml])
AC_OUTPUT
<?xml version="1.0" encoding="iso-8859-1"?>
<bookinfo>
<title>The Glasgow Haskell Compiler User's Guide, Version 6.3</title>
<title>The @PACKAGE_NAME@ User's Guide, Version @PACKAGE_VERSION@</title>
<author><othername>The GHC Team</othername></author>
<address>
<email>glasgow-haskell-&lcub;bugs,users&rcub;-request@haskell.org</email>
......
......@@ -8,7 +8,7 @@
# This file is subject to the same free software license as GHC.
%define name ghc
%define version @version@
%define version @PACKAGE_VERSION@
%define release @release@
Name: %{name}
......
......@@ -36,8 +36,8 @@
ProjectName = The Glorious Glasgow Haskell Compilation System
ProjectNameShort = ghc
ProjectVersion = 6.3
ProjectVersionInt = 603
ProjectVersion = @PACKAGE_VERSION@
ProjectVersionInt = @ProjectVersionInt@
ProjectPatchLevel = 0
# Interface file version (hi-boot files only)
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment