You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Suggestion
The current building module dir, /run/build/ModuleName is unique and different for each module.
While FLATPAK_BUILDER_BUILDDIR environment variable is available in the building instance, it can't be used in the env property.
I suggest adding the symlink /run/build/.current that will point to /run/build/ModuleName.
This will help avoid having to set per-module environment variables, like these used for building Node.js modules, Golang, etc. Instead, it would be possible to set these variables globally or using a YAML alias, making the Flatpak manifest shorter, more concise, and require less maintenance.
The text was updated successfully, but these errors were encountered:
Checklist
Suggestion
The current building module dir,
/run/build/ModuleName
is unique and different for each module.While
FLATPAK_BUILDER_BUILDDIR
environment variable is available in the building instance, it can't be used in theenv
property.I suggest adding the symlink
/run/build/.current
that will point to/run/build/ModuleName
.This will help avoid having to set per-module environment variables, like these used for building Node.js modules, Golang, etc. Instead, it would be possible to set these variables globally or using a YAML alias, making the Flatpak manifest shorter, more concise, and require less maintenance.
The text was updated successfully, but these errors were encountered: