public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-pms] [PATCH 2/6] best_version: Explicitly specify the output format
Date: Tue, 1 May 2018 13:33:45 +0200	[thread overview]
Message-ID: <23272.20633.915380.769616@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20180501112401.7606-3-mgorny@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

>>>>> On Tue, 1 May 2018, Michał Górny wrote:

> Explain the format used by best_version command explicitly.  Currently,
> the function only lists what gets printed but not in what form or how it
> is separated.
> ---
>  pkg-mgr-commands.tex | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)

> diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex
> index cb704f0..4299624 100644
> --- a/pkg-mgr-commands.tex
> +++ b/pkg-mgr-commands.tex
> @@ -105,8 +105,9 @@ are given, \t{-r} is assumed.
>  \item[has_version] Takes exactly one package dependency specification as an argument. Returns
>      true if a package matching the specification is installed, and false otherwise.
>  \item[best_version] Takes exactly one package dependency specification as an argument. If a
> -    matching package is installed, prints the category, package name and version of the highest
> -    matching version; otherwise, prints an empty string. The exit code is unspecified.
> +    matching package is installed, prints the category, followed by \t{/}, followed by package
> +    name, followed by \t{-}, followed by full version of the highest matching version;

Do we really need this? I think that "category, package name and
version" is pretty clear.

> +    otherwise, prints an empty string. The exit code is unspecified.
>  \end{description}
 
>  \ChangeWhenAddingAnEAPI{7}
> -- 
> 2.17.0

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2018-05-01 11:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 11:23 [gentoo-pms] [PATCH 0/6] Ebuild-specific commands clarification & cleanup Michał Górny
2018-05-01 11:23 ` [gentoo-pms] [PATCH 1/6] nonfatal: Reword argument handling to be cleaner Michał Górny
2018-05-01 11:23 ` [gentoo-pms] [PATCH 2/6] best_version: Explicitly specify the output format Michał Górny
2018-05-01 11:33   ` Ulrich Mueller [this message]
2018-05-01 11:49     ` Michał Górny
2018-05-01 11:49     ` Ulrich Mueller
2018-05-01 11:23 ` [gentoo-pms] [PATCH 3/6] Account for 'Build commands' being run in src_test Michał Górny
2018-05-01 11:23 ` [gentoo-pms] [PATCH 4/6] *into, *opts: Reword to use 'as ...' wording from 'do*' Michał Górny
2018-05-01 11:24 ` [gentoo-pms] [PATCH 5/6] *into, *opts: Clarify the number of arguments Michał Górny
2018-05-01 11:35   ` Ulrich Mueller
2018-05-01 11:24 ` [gentoo-pms] [PATCH 6/6] *into, *opts: Remove redundant offset-prefix sentence from heading Michał Górny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23272.20633.915380.769616@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-pms@lists.gentoo.org \
    --cc=mgorny@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox