Fix monorepo bug wrt location of generated manifest (#1684)
* Fix monorepo bug wrt location of generated manifest
When deploying crates, to avoid confusion, we replace the packaged manifest (if
any) with the one from the index, which is the one used anyway. For monorepos,
the replacement was placed at the repo root instead of at the crate location.
Fix monorepo bug wrt location of generated manifest (#1684)
* Fix monorepo bug wrt location of generated manifest
When deploying crates, to avoid confusion, we replace the packaged manifest (if
any) with the one from the index, which is the one used anyway. For monorepos,
the replacement was placed at the repo root instead of at the crate location.
tali auster [Mon, 18 Mar 2024 16:12:16 +0000 (10:12 -0600)]
dev/build.sh: control build jobs with $ALIRE_BUILD_JOBS (#1651)
This is just a minor quality-of-life improvement for packaging. Note
that this also quotes the argument to echo so that if (somehow)
$ALIRE_OS were set to a malicious value, no harm could be done.
Francesc Rocher [Mon, 18 Mar 2024 17:59:49 +0000 (18:59 +0100)]
Rename switch arguments to indicate expected type (#1650)
In commands with options that admit arguments, like '--prefix' in
'alr install', is useful to provide an argument name in the command
help that gives a hint of the expected type.
For example, 'alr install -h' shows the message:
====
OPTIONS
--prefix=ARG Override installation prefix (default is ...)
====
When changed to:
====
OPTIONS
--prefix=DIR Override installation prefix (default is ...)
====
the 'DIR' name of the argument immediately says what is expected in this
option. In cases where this is not so obvious, it helps even more.
For example, in 'alr build -h':
====
OPTIONS
--profiles=LIST Comma-separated list of <crate>=<profile> values (see description)
--stop-after=STAGE Build stage after which to stop (see description)
====
is a quick remainder of what is expected in that options.
Francesc Rocher [Mon, 18 Mar 2024 17:59:49 +0000 (18:59 +0100)]
Rename switch arguments to indicate expected type (#1650)
In commands with options that admit arguments, like '--prefix' in
'alr install', is useful to provide an argument name in the command
help that gives a hint of the expected type.
For example, 'alr install -h' shows the message:
====
OPTIONS
--prefix=ARG Override installation prefix (default is ...)
====
When changed to:
====
OPTIONS
--prefix=DIR Override installation prefix (default is ...)
====
the 'DIR' name of the argument immediately says what is expected in this
option. In cases where this is not so obvious, it helps even more.
For example, in 'alr build -h':
====
OPTIONS
--profiles=LIST Comma-separated list of <crate>=<profile> values (see description)
--stop-after=STAGE Build stage after which to stop (see description)
====
is a quick remainder of what is expected in that options.
tali auster [Mon, 18 Mar 2024 16:12:16 +0000 (10:12 -0600)]
dev/build.sh: control build jobs with $ALIRE_BUILD_JOBS (#1651)
This is just a minor quality-of-life improvement for packaging. Note
that this also quotes the argument to echo so that if (somehow)
$ALIRE_OS were set to a malicious value, no harm could be done.
Both 'alr -c' and 'alr --config' throw exceptions because a required
parameter is missing.
This fix handle missing parameter of config switch in the same way as, for
example, 'alr -C' and 'alr --chdir': an error message informs the user that a
required parameter is missing.
Clearer identification of missing dependencies (#1588)
When a complete solution is printed (`alr show|with --solve`), the "external"
section is now named "missing" (which is what it actually meant).
When a diff is show that contains missing dependencies, a new section is
appended containing separately all missing dependencies, labeled as such:
```
$ alr -f with hello unobtanium
Requested changes:
✓ hello ^1.0.2 (add)
✓ unobtanium * (add)
Changes to dependency solution:
New solution is incomplete.
+ hello 1.0.2 (new)
Missing:
+❗ unobtanium * (new,missing:unknown)
```
Fabien Chouteau [Fri, 23 Feb 2024 10:39:46 +0000 (11:39 +0100)]
Alr.Commands.Search: change default behavior to include properties (#1575)
* Alr.Commands.Search: change default behavior to include properties
This patch comes from a comment of a user looking for gnatpp in Alire.
gnatpp is part of the libabalang_tools crate and a 1.x `alr search gnatpp`
returns nothing. The reason that by default only the release name and
descriptions are searched. This is quite a bad user interaction.
Here we change the default behavior to search in all properties of a
release, including tags, executables, website, etc.
We also display the list of properties that match the pattern.
Searching in names and descriptions only is still possible with the
--crates switch.
* Alr.Commands.Search: use a set rather than a vector for matching props
This test is dependent on a remote repo (`test-index`) on which a PR is opened
during testing, so we better run this one sporadically and locally, or in a
single selected CI configuration.
* Self-review
* Use `ALIRE_TESTSUITE_*` for testsuite env variables
Fabien Chouteau [Thu, 8 Feb 2024 18:03:25 +0000 (19:03 +0100)]
Remove blue background setting from Windows shortcut (#1555)
The shortcut from the Windows installer was setting a background color for PowerShell command prompt. The idea was to match the look of the PowerShell you would normally start, and avoid confusion with the CMD prompt which has a black background. But that didn't work very well as the background color just disappeared when running commands. Also it seems like Windows now uses a black background for the PowerShell anyway.
projects / alire.git / log