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
{{ message }}
This repository has been archived by the owner on Jun 10, 2019. It is now read-only.
In the manifest file, the packages.install and packages.trusted-keys requires an absolute path to files. This is problematic since it makes it impossible to perform the build from any directory without first modifying the manifest file.
Quickly looking at the code, both InstallPackages and InstallTrustedKeys seems like they should be able to handle relative paths, as well as absolute paths.
To be able to distinguish a package name from a relative path in packages.install, I suggest using the same method as apt-get install, where relative paths starts with ./.
The text was updated successfully, but these errors were encountered:
Sounds like a great idea. Relative paths have been introduced in other parts of the manifest as well. We should stay with the practice of making them relative to the manifest as done in #341.
In the manifest file, the
packages.install
andpackages.trusted-keys
requires an absolute path to files. This is problematic since it makes it impossible to perform the build from any directory without first modifying the manifest file.Quickly looking at the code, both
InstallPackages
andInstallTrustedKeys
seems like they should be able to handle relative paths, as well as absolute paths.To be able to distinguish a package name from a relative path in
packages.install
, I suggest using the same method asapt-get install
, where relative paths starts with./
.The text was updated successfully, but these errors were encountered: