Hello community,
here is the log from the commit of package check
checked in at Thu Apr 10 13:10:29 CEST 2008.
--------
--- check/check.changes 2007-03-27 12:43:08.000000000 +0200
+++ /mounts/work_users/ro/BASELIBS.OUT/check/check.changes 2008-04-10 12:57:11.025407000 +0200
@@ -1,0 +2,6 @@
+Thu Apr 10 12:54:45 CEST 2008 - ro@suse.de
+
+- added baselibs.conf file to build xxbit packages
+ for multilib support
+
+-------------------------------------------------------------------
New:
----
baselibs.conf
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ check.spec ++++++
--- /var/tmp/diff_new_pack.hK5000/_old 2008-04-10 13:10:24.000000000 +0200
+++ /var/tmp/diff_new_pack.hK5000/_new 2008-04-10 13:10:24.000000000 +0200
@@ -1,7 +1,7 @@
#
# spec file for package check (Version 0.9.5)
#
-# Copyright (c) 2007 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2008 SUSE LINUX Products GmbH, Nuernberg, Germany.
# This file and all modifications and additions to the pristine
# package are under the same license as the package itself.
#
@@ -10,23 +10,24 @@
# norootforbuild
+
Name: check
Version: 0.9.5
-Release: 1
-URL: http://check.sourceforge.net/
+Release: 63
+Url: http://check.sourceforge.net/
Group: Development/Libraries/C and C++
-License: GNU Library General Public License v. 2.0 and 2.1 (LGPL)
+License: LGPL v2.1 or later
Summary: Unit Test Framework for C
Source: %{name}-%{version}.tar.bz2
BuildRoot: %{_tmppath}/%{name}-%{version}-build
%description
-Check is a unit test framework for C. It features a simple interface
-for defining unit tests, putting little in the way of the developer.
-Tests are run in a separate address space, so Check can catch both
-assertion failures and code errors that cause segmentation faults or
-other signals. The output from unit tests can be used within source
-code editors and IDEs.
+Check is a unit test framework for C. It features a simple interfacefor
+defining unit tests, limitating the developer the less possible. Tests
+are run in a separate address space, so Check cancatch both, assertion
+failures and code errors that cause segmentationfaults or other
+signals. The output of unit tests can be used within source code
+editors and IDEs.
@@ -37,6 +38,7 @@
Sven Neumann