| 2022-08-15 12:32:13 |
Robert P. J. Day |
description |
I can see that if I'm running commands like "snapcraft plugins", if I happen to be at the top of a snap build directory, then the command will use the base specified in the snapcraft.yaml file.
However, if I'm some (non-snap/) subdirectory of that build directory, then the command reverts to simply using the latest supported base. Would it be difficult to extend snapcraft's behaviour to act more like Git, in that no matter where you are in a build directory, the base from the snapcraft.yaml file associated with that build directory will be used? That would be more consistent behaviour. |
I can see that if I'm running commands like "snapcraft plugins", if I happen to be at the top of a snap build directory, then the command will use the base specified in the snapcraft.yaml file.
However, if I'm in some (non-snap/) subdirectory of that build directory, then the command reverts to simply using the latest supported base. Would it be difficult to extend snapcraft's behaviour to act more like Git, in that no matter where you are in a build directory, the base from the snapcraft.yaml file associated with that build directory will be used? That would be more consistent behaviour. |
|
