autotools plugin should still honour autogen.sh if present
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Abandoned. The request for the autotools plugin v2 to preserve autogen.sh execution was closed without resolution, leaving the plugin to skip autogen.sh and run autoreconf directly.
Suggested action: —
No scores available.
Issue body
The version 2 autotools plugin being released with snapcraft 4.0 changes behaviour. In the version 1 tool, the plugin would:
- run ./configure if present
- run autogen.sh or bootstrap if ./configure not present
- run autoreconf --install if ./configure, autogen.sh and bootstrap are all missing
The version 2 plugin will:
- run ./configure if present
- run autoreconf --install if ./configure is not present
The version 2 behaviour is reasonable for most cases, as the contents of "autogen.sh" is often only "autoreconf -i". However, some projects use more magic in "autogen.sh" (such as sed substitutions etc) which now require manual intervention from the snapcrafter. Shouldn't we honour the upstream build process unless there's a good reason to manually override?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The request for the autotools plugin v2 to preserve autogen.sh execution was closed without resolution, leaving the plugin to skip autogen.sh and run autoreconf directly. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The request to preserve autogen.sh execution in the autotools plugin v2 was abandoned, leaving the current behavior that skips autogen.sh in favor of autoreconf unchanged. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The request to restore autogen.sh execution in the autotools plugin v2 received no discussion, resulting in an abandoned issue with no fix or merge. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1695081 autotools plugin should support explicit autogen or autoreconf | snapcraft (launchpad) | open | Feature request (2015) for the autotools plugin to support explicit autogen/autoreconf steps. No comments or labels; core request since implemented in the autotools v2 plugin via autogen.sh and bootstrap support (PR #3398). | |
| #1507648 Autotools doesn't work without autogen.sh | snapcraft (launchpad) | closed | Adding an autoreconf option instead of autogen.sh was closed without comments or resolution, indicating the feature request was abandoned. No build system changes were implemented. | |
| #11 Autotools doesn't work without autogen.sh | snapcraft | closed | Closed as abandoned. Maintainer rejected the suggestion to replace autogen.sh with autoreconf, citing missing tests. No fix was implemented. | |
| #3398 autotools v2 plugin: support autogen.sh and bootstrap | snapcraft | merged | Merged into master. Adds autogen.sh and bootstrap script support to the autotools v2 plugin. Approved by reviewer, passed CI, and maintained coverage. | |
| #3694 autotools v1 plugin: fix fatal crash when running autogen.sh or bootstrap | snapcraft | closed | Superseded by pull request #3739. The autotools v1 plugin crash fix was closed without merging after three weeks of review inactivity. | |
| #1536700 autotools plugin doesn't call make | snapcraft (launchpad) | closed | Closed without discussion, likely abandoned. The autotools plugin was reported to skip the make step before make install, causing build failures for some projects. | |
| #1661424 autotools plugin crashes while running ./configure | snapcraft (launchpad) | closed | Closed without resolution or comments. The autotools plugin crash during ./configure due to a missing Python interpreter was not fixed and appears abandoned. |