New alr printenv --last-build
#1444
Conversation
src/alr/alr-commands-printenv.adb
Outdated
| Define_Switch (Config, | ||
| Cmd.Last_Build'Access, | ||
| "", "--last-build", | ||
| "Use last build profiles instead of manifest profiles"); |
There was a problem hiding this comment.
I don't understand the use for this switch.
There was a problem hiding this comment.
With the new shared builds the actual paths change depending on the build profile.
Now, alr printenv relies on the info in the manifests, always printing the same info. With this, one could do
alr build --profiles=*=validation
alr printenv --last-build
and get the paths for validation builds.
There was a problem hiding this comment.
I would consider this to be the default behavior. We already save the last build profile somewhere, right?
There was a problem hiding this comment.
Yes, they're saved after every build. That's what's being used to set the profiles here indeed.
We could make alr printenv understand the --profiles switch too, in case one wants to get a particular environment without forcing a build in advance.
This may be useful when no direct editing of manifests is convenient, as otherwise `printenv` will always use the manifest's configuration.
mosteo
force-pushed
the
feat/printenv-saved-profile
branch
2 times, most recently
from
0552e9d
to
4f0df6b
Compare
mosteo
force-pushed
the
feat/printenv-saved-profile
branch
from
f64ba88
to
393d4ce
Compare
|
Modified to make this the default behavior |
This may be useful when no direct editing of manifests is convenient, as otherwise
printenvwill always use the manifest's configuration.