$SNAPCRAFT_PROJECT_NAME used in a remote part expands to wrong value

Bug #1766878 reported by Daniel Llewellyn on 2018-04-25
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Snapcraft
Undecided
Unassigned

Bug Description

In my alsa remote part I've attempted to use $SNAPCRAFT_PROJECT_NAME to build a path to the final snap installation directory expecting it to expand to the name of the consuming snapcraft.yaml. Instead it expands to `alsa` because that's the name on the snapcraft.yaml containing the remote part. This is counter-intuitive; I expect $SNAPCRAFT_PROJECT_NAME to always be the project that snapcraft started building - i.e. the consumer of the remote part, and not the name of any remote parts included as a dependency.

Changed in snapcraft:
status: New → Confirmed
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers