Search
j0ke.net Open Build Service
>
Projects
>
graphics
:
ImageMagick:6.9.1.10
>
autoconf
> autoconf-testsuite.spec
Sign Up
|
Log In
Username
Password
Cancel
Overview
Repositories
Revisions
Requests
Users
Advanced
Attributes
Meta
File autoconf-testsuite.spec of Package autoconf
# # spec file for package autoconf-testsuite # # Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # Name: autoconf-testsuite Version: 2.69 Release: 0 Summary: A GNU Tool for Automatically Configuring Source Code License: GPL-3.0+ Group: Development/Tools/Building Url: http://www.gnu.org/software/autoconf Source0: http://ftp.gnu.org/gnu/autoconf/autoconf-%{version}.tar.gz Source1: http://ftp.gnu.org/gnu/autoconf/autoconf-%{version}.tar.gz.sig Source2: %{name}.keyring Patch0: autoreconf-ltdl.diff BuildRequires: help2man Requires: info Requires: m4 >= 1.4.6 Requires: perl >= 5.6 Requires(post): %{install_info_prereq} Requires(preun): %{install_info_prereq} BuildRoot: %{_tmppath}/%{name}-%{version}-build BuildArch: noarch %description GNU Autoconf is a tool for configuring source code and makefiles. Using autoconf, programmers can create portable and configurable packages, because the person building the package is allowed to specify various configuration options. You should install autoconf if you are developing software and would like to create shell scripts to configure your source code packages. Note that the autoconf package is not required for the end user who may be configuring software with an autoconf-generated script; autoconf is only required for the generation of the scripts, not their use. %prep %setup -q -n autoconf-%{version} %patch0 %build %configure make %{?_smp_mflags} %if "%{name}" == "autoconf-testsuite" %check trap 'test $? -ne 0 && cat tests/testsuite.log' EXIT make %{?_smp_mflags} check %install %else %install %{?make_install} %{!?make_install:make install DESTDIR=%{buildroot}} rm -f %{buildroot}%{_datadir}/emacs/site-lisp/*.el* # info's dir file is not auto ignored on some systems rm -rf %{buildroot}%{_infodir}/dir %endif %post %install_info --info-dir=%{_infodir} %{_infodir}/autoconf.info.gz %preun %install_info_delete --info-dir=%{_infodir} %{_infodir}/autoconf.info.gz %if "%{name}" == "autoconf" %files %defattr(-,root,root) %doc AUTHORS COPYING NEWS README TODO %{_bindir}/* %{_datadir}/autoconf %doc %{_infodir}/*.gz %doc %{_mandir}/man1/*.gz %endif %changelog