#9 [DO NOT MERGE HERE] Initial version of compat package autoconf2.69
Opened 2 years ago by odubaj. Modified 2 years ago
rpms/ odubaj/autoconf autoconf-compat-2.69  into  rawhide

autoconf2.69.spec autoconf.spec
file renamed
+19 -13
@@ -3,22 +3,27 @@ 

  # Run extended test

  %bcond_without autoconf_enables_optional_test

  

- Summary:    A GNU tool for automatically configuring source code

- Name:       autoconf

+ Summary:    A compatibility package for autoconf

  Version:    2.69

- Release:    36%{?dist}

+ Release:    37%{?dist}

+ Name:       autoconf%{version}

  License:    GPLv2+ and GFDL

  Source0:    https://ftp.gnu.org/gnu/autoconf/autoconf-%{version}.tar.xz

  Source1:    config.site

  Source2:    autoconf-init.el

  URL:        https://www.gnu.org/software/autoconf/

  

- Patch1:     autoconf-2.69-perl-5.22-autoscan.patch            

+ # Porting autoscan to perl-5.17

+ Patch1:     autoconf-2.69-perl-5.22-autoscan.patch

+ # Porting tests to Bash 5

  Patch2:     autoconf-2.69-bash-5-LINENO.patch

+ # Backport --runstatedir option from version 2.70

  Patch3:     autoconf-2.69-backport-runstatedir-option.patch

  

  BuildArch:  noarch

  

+ Conflicts:  autoconf

+ Provides:   autoconf = %{version}-%{release}

  

  # run "make check" by default

  %bcond_without check
@@ -64,19 +69,17 @@ 

  packages, since 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 that configure your source code

- packages. If you are installing Autoconf, you will also need to

- install the GNU m4 package.

+ You should install Autoconf2.69 if you are developing older software

+ and would like to create shell scripts that 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.

+ Please note, this package is older version of official autoconf package,

+ which was created due to compatibility reasons, as the newest version of

+ autoconf is not ABI compatible with the older one.

  

  

  %prep

- %autosetup -p1

+ %autosetup -p1 -n autoconf-%{version}

  

  %build

  %if %{with autoconf_enables_emacs}
@@ -126,6 +129,9 @@ 

  

  

  %changelog

+ * Tue Mar 02 2021 Ondrej Dubaj <odubaj@redhat.com> - 2.69-37

+ - Create compat package autoconf2.69

+ 

  * Tue Jan 26 2021 Fedora Release Engineering <releng@fedoraproject.org> - 2.69-36

  - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild

  

no initial comment

rebased onto 909535d

2 years ago

Build succeeded.

I'd keep it >= 36. It makes better sense to me than resetting.

Don't forget to rename the spec file as well. I'd do it in the same commit.
This PR cannot be merged here, but once you request the dist-git repo for autoconf2.69, you can request it with --no-initial-commit and push the history of autoconf and this PR to it.

The name in the changelog is without dot.

Consider also adding: Provides: autoconf = %{version}-%{release}
That way, if somebody BuldRequires e.g. autoconf < 37, they'll get this. Also it will allow package to BRs this compat package and also transitively BR just autotools.

Consider defining version first and using Name: autoconf%{version}

Don't forget to rename the spec file as well. I'd do it in the same commit.
This PR cannot be merged here, but once you request the dist-git repo for autoconf2.69, you can request it with --no-initial-commit and push the history of autoconf and this PR to it.

Sure, this is just a way to show the incoming changes, another review will be done during new ackage review process

I'd also update the summary and description to mention that this is an older version of autotools and the newer version is available in the autoools package.

Otherwise this looks good to me.

rebased onto 92b5326

2 years ago

rebased onto fbdcd00

2 years ago

Done, thanks for review!

rebased onto 09b930d

2 years ago

Looking good but I haven't tested the conflict/provide. I can do that if you have a scratchbuild with the new autoconf.

Build succeeded.

rebased onto c0cfa4b

2 years ago

I've renamed the PR so nobody accidentally merges it.

Build succeeded.

Metadata