1 |
>>>>> On Tue, 1 May 2018, Michał Górny wrote: |
2 |
|
3 |
> Explain the format used by best_version command explicitly. Currently, |
4 |
> the function only lists what gets printed but not in what form or how it |
5 |
> is separated. |
6 |
> --- |
7 |
> pkg-mgr-commands.tex | 5 +++-- |
8 |
> 1 file changed, 3 insertions(+), 2 deletions(-) |
9 |
|
10 |
> diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex |
11 |
> index cb704f0..4299624 100644 |
12 |
> --- a/pkg-mgr-commands.tex |
13 |
> +++ b/pkg-mgr-commands.tex |
14 |
> @@ -105,8 +105,9 @@ are given, \t{-r} is assumed. |
15 |
> \item[has_version] Takes exactly one package dependency specification as an argument. Returns |
16 |
> true if a package matching the specification is installed, and false otherwise. |
17 |
> \item[best_version] Takes exactly one package dependency specification as an argument. If a |
18 |
> - matching package is installed, prints the category, package name and version of the highest |
19 |
> - matching version; otherwise, prints an empty string. The exit code is unspecified. |
20 |
> + matching package is installed, prints the category, followed by \t{/}, followed by package |
21 |
> + name, followed by \t{-}, followed by full version of the highest matching version; |
22 |
|
23 |
Do we really need this? I think that "category, package name and |
24 |
version" is pretty clear. |
25 |
|
26 |
> + otherwise, prints an empty string. The exit code is unspecified. |
27 |
> \end{description} |
28 |
|
29 |
> \ChangeWhenAddingAnEAPI{7} |
30 |
> -- |
31 |
> 2.17.0 |