snapcraft should setup search paths/flags for parts built after parts
Metadata
Current evaluation
Closed without resolution. The request to auto-configure search paths for dependent parts was abandoned. Later snapcraft updates added native environment propagation and part dependency handling, rendering the feature obsolete.
Suggested action: —
No scores available.
Issue body
When building multiple parts from source that depend on each other in a snapcraft session it would be useful if snapcraft would setup the environment for each part in a way that autotools/pkg-config/cmake can find the build results from 'after:'-parts.
Or instead of setting up search paths it might just build & install in a dedicated chroot environment and build each part in the same environment..
Assume this snapcraft.yaml:
name: nfs-server # the name of the snap
version: 0.1 # the version of the snap
# The vendor for the snap (replace 'Vendor <email address hidden>')
vendor: Andreas Pokorny <email address hidden>
summary: Simple NFS Server
description: Simple NFS Server setup for home server use, with manual user and exports setup
icon: folder-remote-nfs.png
architectures: [armhf]
parts:
libtirpc:
plugin: autotools
source: git://github.com/APokorny/libtirpc.git
source-branch: use-snappy-env
stage-packages:
- libkrb5-dev
filesets:
tir-files:
- lib/libtirpc.so*
snap:
- $tir-files
rpcbind:
plugin: autotools
source: git://git.linux-nfs.org/projects/steved/rpcbind.git
stage-packages:
- libwrap0-dev
after:
- libtirpc
nfs-utils:
plugin: autotools
source: git://github.com/APokorny/nfs-utils.git
source-branch: use-snappy-env
stage-packages:
- libcomerr2
- libnfsidmap2
after:
- libtirpc
After building libtirpc when building rpcbind configure fails because it cannot find libtirpc. The configure script uses pkg-config here. I assume snapcraft would use PKG_CONFIG_PATH and PKG_CONFIG_SYSROOT_DIR.
...
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The request to auto-configure search paths for dependent parts was abandoned. Later snapcraft updates added native environment propagation and part dependency handling, rendering the feature obsolete. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments or resolution. The requested automatic environment setup was later implemented in subsequent snapcraft releases, superseding this issue. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation or comments. The request to automatically configure search paths for dependent parts was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1778081 Snapcraft saves the fact that parts need to be rebuilt rather than discovering them | snapcraft (launchpad) | closed | Closed without implementation. The dynamic dependency discovery approach for build caching was abandoned and superseded by later Snapcraft caching architecture updates. | |
| #1622435 snapcraft does not respect filesets of remote parts | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft failed to resolve remote part filesets, causing build errors. Likely abandoned or superseded by newer versions. The wiki label indicates the workflow was clarified via documentation. | |
| #1659085 snapcraft needs to migrate to a snap directory | snapcraft (launchpad) | closed | Closed without resolution. The proposed migration of snapcraft to a snap directory, including build artifact relocation and plugin updates, was abandoned or superseded by subsequent architecture changes. | |
| #1815658 snapcraft leaks build-environment across parts | snapcraft (launchpad) | closed | Closed without comments. Reports snapcraft build-environment variables leaking across parts. Likely abandoned due to inactivity, with no explicit resolution or fix noted. | |
| #1799925 snapcraft gives conflicting advice for cleaning parts | snapcraft (launchpad) | closed | Closed without a fix. Snapcraft incorrectly advised running snapcraft clean with part and step flags, which were unsupported. The author worked around it with a full clean. The report appears abandoned or superseded by later updates. | |
| #1897337 snapcraft build <part> ignores the part | snapcraft (launchpad) | closed | The snapcraft build command ignoring specified parts was closed without a fix or resolution. No comments or patches were provided, indicating the report was abandoned without addressing the filtering behavior. | |
| #1677974 snap build dependencies | snapcraft (launchpad) | closed | Closed without resolution. The request to specify snap packages as build dependencies in snapcraft.yaml appears abandoned or superseded by upstream Snapcraft updates that later added native build dependency support. | |
| #1750866 Remote parts can't depend on other remote parts | snapcraft (launchpad) | closed | Closed as abandoned due to inactivity. Snapcraft does not automatically pull in dependent remote parts, requiring manual specification in the snap.yaml. | |
| #1816 snapcraft update won't fetch from `SNAPCRAFT_PARTS_URI` | snapcraft | closed | Closed without resolution or comments. Likely superseded by the linked Launchpad bug report. No fixes or code changes were applied. |