Mailinglist Archive: opensuse-commit (1066 mails)

< Previous Next >
commit xorg-x11-libs for openSUSE:Factory
  • From: root@xxxxxxxxxxxxxxx (h_root)
  • Date: Mon, 13 Dec 2010 12:31:44 +0100
  • Message-id: <20101213113144.A9276202B1@xxxxxxxxxxxxxxx>

Hello community,

here is the log from the commit of package xorg-x11-libs for openSUSE:Factory
checked in at Mon Dec 13 12:31:44 CET 2010.

--- xorg-x11-libs/xorg-x11-libs.changes 2010-12-01 12:50:15.000000000 +0100
+++ xorg-x11-libs/xorg-x11-libs.changes 2010-12-09 13:01:46.000000000 +0100
@@ -1,0 +2,13 @@
+Thu Dec 9 11:31:02 UTC 2010 - sndirsch@xxxxxxxxxx
+- xbitmaps 1.1.1
+ * This minor maintenance release mostly provides the usual
+ collection of janitorial cleanups and build configuration
+ improvements.
+ It also changes the installation path for the pkg-config
+ xbitmaps.pc from $(libdir) to $(datadir), as no libraries
+ or compiled code are found via this pkg-config file, only
+ platform-independent image files (which double as C source
+ code headers that programs may #include at compile time).

calling whatdependson for head-i586




Other differences:
++++++ xorg-x11-libs.spec ++++++
--- /var/tmp/diff_new_pack.9aJjfM/_old 2010-12-13 12:30:40.000000000 +0100
+++ /var/tmp/diff_new_pack.9aJjfM/_new 2010-12-13 12:30:40.000000000 +0100
@@ -34,7 +34,7 @@
Version: 7.5
-Release: 14
+Release: 15
License: GPLv2+ ; MIT License (or similar)
BuildRoot: %{_tmppath}/%{name}-%{version}-build
Group: System/Libraries
@@ -63,7 +63,7 @@
Source23: liblbxutil-1.1.0.tar.bz2
Source24: liboldX-X11R7.0-1.0.1.tar.bz2
Source25: libxkbui-X11R7.1-1.0.2.tar.bz2
-Source26: xbitmaps-1.1.0.tar.bz2
+Source26: xbitmaps-1.1.1.tar.bz2
Source27: libXres-1.0.5.tar.bz2
Source29: libvnc-20070501.tar.bz2
Source30: libXcliplist-20070501.tar.bz2
@@ -298,6 +298,7 @@
%exclude /usr/%{_lib}/
%exclude /usr/%{_lib}/pkgconfig/pciaccess.pc
%doc %{_datadir}/doc/libXvMC/
%doc %{_datadir}/doc/libXaw/

++++++ xbitmaps-1.1.0.tar.bz2 -> xbitmaps-1.1.1.tar.bz2 ++++++
++++ 8405 lines of diff (skipped)
++++ retrying with extended exclude list
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' --exclude --exclude configure --exclude
config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4
--exclude config.sub --exclude depcomp --exclude install-sh --exclude
old/xbitmaps-1.1.0/ChangeLog new/xbitmaps-1.1.1/ChangeLog
--- old/xbitmaps-1.1.0/ChangeLog 2009-10-13 07:11:28.000000000 +0200
+++ new/xbitmaps-1.1.1/ChangeLog 2010-12-09 07:26:27.000000000 +0100
@@ -1,3 +1,134 @@
+commit df1dfeaee913f6ce1f82189b90493c14cb011564
+Author: Alan Coopersmith <alan.coopersmith@xxxxxxxxxx>
+Date: Wed Dec 8 22:25:45 2010 -0800
+ xbitmaps 1.1.1
+ Signed-off-by: Alan Coopersmith <alan.coopersmith@xxxxxxxxxx>
+commit ba8d08a029c82aeb60b8c24fad76de8be288022b
+Author: Alan Coopersmith <alan.coopersmith@xxxxxxxxxx>
+Date: Wed Nov 10 20:12:11 2010 -0800
+ Install xbitmaps.pc to $(datadir)/pkgconfig instead of $(libdir)
+ The xbitmaps package consists entirely of X bitmap data files, which
+ are platform-independent text files containing a C language format
+ representation of the encoded bitmap image, which are installed to
+ $(includedir)/X11/bitmaps so that programs can #include them into
+ their sources at build time.
+ Signed-off-by: Alan Coopersmith <alan.coopersmith@xxxxxxxxxx>
+ Acked-by: Peter Hutterer <peter.hutterer@xxxxxxxxx>
+commit 5c89f362c67dadd858f3001d5cc79a8cb86e4a3d
+Author: Alan Coopersmith <alan.coopersmith@xxxxxxxxxx>
+Date: Wed Nov 10 20:09:29 2010 -0800
+ config: replace deprecated AM_CONFIG_HEADER with AC_CONFIG_HEADERS
+ Regroup AC statements under the Autoconf initialization section.
+ Regroup AM sttaements under the Automake initialization section.
+ Add missing AC_CONFIG_SRCDIR
+ Signed-off-by: Alan Coopersmith <alan.coopersmith@xxxxxxxxxx>
+commit a908a28058b299390b250db7fccca078fa1f4065
+Author: Gaetan Nadon <memsize@xxxxxxxxxxxx>
+Date: Mon Mar 29 13:24:09 2010 -0400
+ config: update AC_PREREQ statement to 2.60
+ Unrelated to the previous patches, the new value simply reflects
+ the reality that the minimum level for autoconf to configure
+ all modules is 2.60 dated June 2006.
+ Signed-off-by: Gaetan Nadon <memsize@xxxxxxxxxxxx>
+commit 48e794ca241e9fe29644a1790115b80733a59669
+Author: Gaetan Nadon <memsize@xxxxxxxxxxxx>
+Date: Mon Mar 29 11:37:20 2010 -0400
+ config: do not clean xbitmaps.pc
+ This file is part of the configuration and is removed
+ by running "make distclean"
+ Signed-off-by: Gaetan Nadon <memsize@xxxxxxxxxxxx>
+commit be7a40a5fd45c2ad6c3ed1ab87537431613691a0
+Author: Gaetan Nadon <memsize@xxxxxxxxxxxx>
+Date: Mon Mar 29 11:35:30 2010 -0400
+ config: remove the pkgconfig file from EXTRA_DIST
+ Automake always includes it in the tarball.
+ Signed-off-by: Gaetan Nadon <memsize@xxxxxxxxxxxx>
+commit 2b5713c691be826ff79617c5e5dfa30614d3cb94
+Author: Gaetan Nadon <memsize@xxxxxxxxxxxx>
+Date: Sun Nov 29 19:33:52 2009 -0500
+ INSTALL, NEWS, README or AUTHORS files are missing/incorrect #24206
+ Automake 'foreign' option is specified in
+ Remove from
+commit c9b67f5c37d78cfaf81a0c7a76de1bd913cbc8f2
+Author: Gaetan Nadon <memsize@xxxxxxxxxxxx>
+Date: Wed Oct 28 14:09:09 2009 -0400
+ INSTALL, NEWS, README or AUTHORS files are missing/incorrect #24206
+ Add missing INSTALL file. Use standard GNU file on building tarball
+ README may have been updated
+ Remove AUTHORS file as it is empty and no content available yet.
+ Remove NEWS file as it is empty and no content available yet.
+commit 2b573f8ba774b474639c2ec1be563fb0bf0de6af
+Author: Gaetan Nadon <memsize@xxxxxxxxxxxx>
+Date: Mon Oct 26 22:08:40 2009 -0400
+ ChangeLog not required: EXTRA_DIST or *CLEANFILES #24432
+ ChangeLog filename is known to Automake and requires no further
+ coding in the makefile.
+commit 4276fdbb9d614f1d29e8c62f8c24c709537947a5
+Author: Gaetan Nadon <memsize@xxxxxxxxxxxx>
+Date: Thu Oct 22 12:34:16 2009 -0400
+ .gitignore: use common defaults with custom section # 24239
+ Using common defaults will reduce errors and maintenance.
+ Only the very small or inexistent custom section need periodic maintenance
+ when the structure of the component changes. Do not edit defaults.
+commit c0527c7664ee7ff6a1eeb14aa5d4715fab86f51a
+Author: Jeremy Huddleston <jeremyhu@xxxxxxxxxxxxxxx>
+Date: Wed Oct 21 12:47:22 2009 -0700
+ This is not a GNU project, so declare it foreign.
+ On Wed, 2009-10-21 at 13:36 +1000, Peter Hutterer wrote:
+ > On Tue, Oct 20, 2009 at 08:23:55PM -0700, Jeremy Huddleston wrote:
+ > > I noticed an INSTALL file in xlsclients and libXvMC today, and it
+ > > was quite annoying to work around since 'autoreconf -fvi' replaces
+ > > it and git wants to commit it. Should these files even be in git?
+ > > Can I nuke them for the betterment of humanity and since they get
+ > > created by autoreconf anyways?
+ >
+ > See
+ As an interim measure, replace AM_INIT_AUTOMAKE([dist-bzip2]) with
+ AM_INIT_AUTOMAKE([foreign dist-bzip2]). This will prevent the generation
+ of the INSTALL file. It is also part of the 24206 solution.
+ Signed-off-by: Jeremy Huddleston <jeremyhu@xxxxxxxxxxxxxxx>
commit 193b9cc84f98af912e15fe7dc8bd16537b6a5f46
Author: Alan Coopersmith <alan.coopersmith@xxxxxxx>
Date: Mon Oct 12 22:10:25 2009 -0700
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' --exclude --exclude configure --exclude
config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4
--exclude config.sub --exclude depcomp --exclude install-sh --exclude
old/xbitmaps-1.1.0/INSTALL new/xbitmaps-1.1.1/INSTALL
--- old/xbitmaps-1.1.0/INSTALL 1970-01-01 01:00:00.000000000 +0100
+++ new/xbitmaps-1.1.1/INSTALL 2010-12-09 07:26:27.000000000 +0100
@@ -0,0 +1,291 @@
+Installation Instructions
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006, 2007, 2008 Free Software Foundation, Inc.
+ This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+Basic Installation
+ Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package. The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+ If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release. If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+ The file `' (or `') is used to create
+`configure' by a program called `autoconf'. You need `' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+The simplest way to compile this package is:
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system.
+ Running `configure' might take a while. While running, it prints
+ some messages telling which features it is checking for.
+ 2. Type `make' to compile the package.
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package.
+ 4. Type `make install' to install the programs and any data files and
+ documentation.
+ 5. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+ 6. Often, you can also type `make uninstall' to remove the installed
+ files again.
+Compilers and Options
+ Some systems require unusual options for compilation or linking that
+the `configure' script does not know about. Run `./configure --help'
+for details on some of the pertinent environment variables.
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+ ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+ *Note Defining Variables::, for more details.
+Compiling For Multiple Architectures
+ You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you can use GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+ With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory. After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
+ On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple `-arch' options to the
+compiler but only a single `-arch' option to the preprocessor. Like
+ ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CPP="gcc -E" CXXCPP="g++ -E"
+ This is not guaranteed to produce working output in all cases, you
+may have to build one architecture at a time and combine the results
+using the `lipo' tool if you have problems.
+Installation Names
+ 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
+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
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+Optional Features
+ Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+Particular systems
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU
+CC is not installed, it is recommended to use the following options in
+order to use an ANSI C compiler:
+ ./configure CC="cc -Ae"
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+ On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its `<wchar.h>' header file. The option `-nodtk' can be used as
+a workaround. If GNU CC is not installed, it is therefore recommended
+to try
+ ./configure CC="cc"
+and if that doesn't work, try
+ ./configure CC="cc -nodtk"
+Specifying the System Type
+ There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on. Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+where SYSTEM can have one of these forms:
+ See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+ If you are _building_ compiler tools for cross-compiling, you should
+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
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+Sharing Defaults
+ If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/' if it exists, then
+`PREFIX/etc/' if it exists. Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+Defining Variables
+ Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
+ ./configure CC=/usr/local2/bin/gcc
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf bug. Until the bug is fixed you can use this workaround:
+ CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
+`configure' Invocation
+ `configure' recognizes the following options to control how it
+ Print a summary of all of the options to `configure', and exit.
+ Print a summary of the options unique to this package's
+ `configure', and exit. The `short' variant lists options used
+ only in the top level, while the `recursive' variant lists options
+ also present in any nested packages.
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+ Alias for `--cache-file=config.cache'.
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to `/dev/null' (any error
+ messages will still be shown).
+ Look for the package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+ Use DIR as the installation prefix. *Note Installation Names::
+ for more details, including other options available for fine-tuning
+ the installation locations.
+ Run the configure checks, but stop before creating any output
+ files.
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' --exclude --exclude configure --exclude
config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4
--exclude config.sub --exclude depcomp --exclude install-sh --exclude
old/xbitmaps-1.1.0/ new/xbitmaps-1.1.1/
--- old/xbitmaps-1.1.0/ 2009-10-13 07:03:24.000000000 +0200
+++ new/xbitmaps-1.1.1/ 2010-11-11 05:10:29.000000000 +0100
@@ -1,10 +1,7 @@
-pkgconfigdir = $(libdir)/pkgconfig
+pkgconfigdir = $(datadir)/pkgconfig
pkgconfig_DATA = xbitmaps.pc

-CLEANFILES = xbitmaps.pc

bitmapdir = $(includedir)/X11/bitmaps

@@ -81,12 +78,13 @@
xlogo64 \

-EXTRA_DIST += ChangeLog

-.PHONY: ChangeLog


-dist-hook: ChangeLog
+dist-hook: ChangeLog INSTALL
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' --exclude --exclude configure --exclude
config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4
--exclude config.sub --exclude depcomp --exclude install-sh --exclude
old/xbitmaps-1.1.0/ new/xbitmaps-1.1.1/
--- old/xbitmaps-1.1.0/ 2009-10-13 07:10:44.000000000 +0200
+++ new/xbitmaps-1.1.1/ 2010-12-09 07:26:16.000000000 +0100
@@ -42,6 +42,9 @@
/* Define to the one symbol short name of this package. */

+/* Define to the home page for this package. */
/* Define to the version of this package. */

diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' --exclude --exclude configure --exclude
config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4
--exclude config.sub --exclude depcomp --exclude install-sh --exclude
old/xbitmaps-1.1.0/ new/xbitmaps-1.1.1/
--- old/xbitmaps-1.1.0/ 2009-10-13 07:10:05.000000000 +0200
+++ new/xbitmaps-1.1.1/ 2010-12-09 07:25:31.000000000 +0100
@@ -1,9 +1,15 @@
-AC_INIT(xbitmaps, [1.1.0],
[], xbitmaps)
+dnl Process this file with autoconf to create configure.
+# Initialize Autoconf
+AC_INIT([xbitmaps], [1.1.1],
+ [], [xbitmaps])

+# Initialize Automake
+AM_INIT_AUTOMAKE([foreign dist-bzip2])

# Require xorg-macros 1.3 or later: XORG_DEFAULT_OPTIONS


Remember to have fun...

To unsubscribe, e-mail: opensuse-commit+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-commit+help@xxxxxxxxxxxx

< Previous Next >
This Thread