Linux workstation

Upstream software project

autoconf213

A GNU Tool for Automatically Configuring Source Code

About autoconf213

A GNU Tool for Automatically Configuring Source Code

This project links 7 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 15.6: 3 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.autoconf213: recorded package coverageFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.63 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
autoconf213
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-2.0-or-later
Metadata completeness
100/100 (not a software quality rating)
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

GNU's Autoconf is a tool for configuring source code and Makefiles. Using Autoconf, programmers can create portable and configurable packages, since the person building the package is allowed to specify various configuration options. You should install Autoconf if you are developing software and you would like to use it to create shell scripts that will configure your source code packages. If you are installing Autoconf, you will also need to install the GNU m4 package. 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.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. autoconf213

    Fedora 43 / Unspecified / source autoconf213

    2.13-58.fc43

    A GNU tool for automatically configuring source code

    noarch43

Fedora 44

  1. autoconf213

    Fedora 44 / Unspecified / source autoconf213

    2.13-60.fc44

    A GNU tool for automatically configuring source code

    noarch44

openSUSE Leap 15.6

  1. autoconf

    openSUSE Leap 15.6 / Development/Tools/Building / source autoconf

    2.69-1.445

    A GNU Tool for Automatically Configuring Source Code

    noarchleap-15.6
  2. autoconf213

    openSUSE Leap 15.6 / Development/Tools/Building / source autoconf213

    2.13-1.25

    A GNU Tool for Automatically Configuring Source Code

    noarchleap-15.6
  3. autoconf-el

    openSUSE Leap 15.6 / Productivity/Editors/Emacs / source autoconf-el

    2.69-1.40

    Emacs mode for editing GNU Autoconf scripts

    noarchleap-15.6

openSUSE Leap 16.0

  1. autoconf213

    openSUSE Leap 16.0 / Unspecified / source autoconf213

    2.13-160000.2.2

    A GNU Tool for Automatically Configuring Source Code

    noarchleap-16.0

openSUSE Tumbleweed

  1. autoconf213

    openSUSE Tumbleweed / Unspecified / source autoconf213

    2.13-29.7

    A GNU Tool for Automatically Configuring Source Code

    noarchtumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.