[Xfce4-commits] r25415 - libxfce4mcs/branches/xfce_4_4

[Olivier Fourdan]

Author: olivier
Date: 2007-04-07 09:23:53 +0000 (Sat, 07 Apr 2007)
New Revision: 25415

Modified:
   libxfce4mcs/branches/xfce_4_4/INSTALL
   libxfce4mcs/branches/xfce_4_4/configure.in.in
Log:
Update version

Modified: libxfce4mcs/branches/xfce_4_4/INSTALL
===================================================================
--- libxfce4mcs/branches/xfce_4_4/INSTALL	2007-04-07 09:13:21 UTC (rev 25414)
+++ libxfce4mcs/branches/xfce_4_4/INSTALL	2007-04-07 09:23:53 UTC (rev 25415)
@@ -1,7 +1,7 @@
 Installation Instructions
 *************************
 
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
 Software Foundation, Inc.
 
 This file is free documentation; the Free Software Foundation gives
@@ -102,16 +102,16 @@
 Installation Names
 ==================
 
-By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc.  You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PREFIX'.
+By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc.  You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX'.
 
    You can specify separate installation prefixes for
 architecture-specific files and architecture-independent files.  If you
-give `configure' the option `--exec-prefix=PREFIX', the package will
-use PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files will still use the regular prefix.
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
 
    In addition, if you use an unusual directory layout you can give
 options like `--bindir=DIR' to specify different values for particular
@@ -159,7 +159,7 @@
 need to know the machine type.
 
    If you are _building_ compiler tools for cross-compiling, you should
-use the `--target=TYPE' option to select the type of system they will
+use the option `--target=TYPE' to select the type of system they will
 produce code for.
 
    If you want to _use_ a cross compiler, that generates code for a
@@ -189,9 +189,14 @@
 
      ./configure CC=/usr/local2/bin/gcc
 
-will cause the specified gcc to be used as the C compiler (unless it is
-overridden in the site shell script).
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).  Here is a another example:
 
+     /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
+configuration-related scripts to be executed by `/bin/bash'.
+
 `configure' Invocation
 ======================
 

Modified: libxfce4mcs/branches/xfce_4_4/configure.in.in
===================================================================
--- libxfce4mcs/branches/xfce_4_4/configure.in.in	2007-04-07 09:13:21 UTC (rev 25414)
+++ libxfce4mcs/branches/xfce_4_4/configure.in.in	2007-04-07 09:23:53 UTC (rev 25415)
@@ -9,10 +9,10 @@
 dnl
 
 dnl Version information
-m4_define([libxfce4mcs_verinfo], [3:4:0])
+m4_define([libxfce4mcs_verinfo], [3:5:0])
 m4_define([libxfce4mcs_version_major], [4])
 m4_define([libxfce4mcs_version_minor], [4])
-m4_define([libxfce4mcs_version_micro], [0])
+m4_define([libxfce4mcs_version_micro], [1])
 m4_define([libxfce4mcs_version_nano], [])   dnl leave this empty to have no nano version
 m4_define([libxfce4mcs_version_build], [r at REVISION@])
 m4_define([libxfce4mcs_version_tag], [])