> but "pacman -F" also takes file paths or regex as an argument, not just
> package names.
It does, yeah. In this case I was going off what `pacman -h` displays for `-F`,
which is just `[packages]`. Should I update both `-h` and `-Fh`, or just the
latter?
On Thu, 26 Nov 2020, at 04:02, Allan Mc
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official pacman repository".
The branch, master has been updated
via 08f4ae709ca00ec9b4c56d92d3cdd7de4e6effc2 (commit)
vi
On 26/11/20 6:53 am, Colin Woodbury wrote:
> Unlike the other main commands, -F was missing its top-level usage line in its
> help output.
>
> Signed-off-by: Colin Woodbury
> ---
> src/pacman/pacman.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/src/pacman/pacman.c b/src/pacman/pa
On 24/11/20 10:39 pm, morganamilo wrote:
> The comment makes it seem that the result itself is an error code. But
> all it does is simply return -1 to indicate an error occured;
>
> diff --git a/lib/libalpm/alpm.h b/lib/libalpm/alpm.h
> index 614a530c..6a7323e0 100644
> --- a/lib/libalpm/alpm.h
>
