izzy Meyer, 2024-12-11 11:53 -0600:
> I agree that the faq15 page should be updated to reflect this behavior.
I've been told off-list that the page will be updated.
> although IMHO, it should specifically mention this quirk only affects
> -stable as the way mirrors architect the repositories mak
--- Original Message
From: Maxim
Sent: December 11, 2024 10:49:27 AM CST
To: misc@openbsd.org, Marc Espie
Cc: Jan Stary
Subject: Re: pkg_info -Q: inconsistent search results
Marc,
What was the rational to put "./" as the first search path in the default
PKG_PATH, in particular? An
Marc,
What was the rational to put "./" as the first search path in the default
PKG_PATH, in particular? And include "./" in there at all, in general?
* * *
Yesterday on Libera Chat we debugged a related problem followed by a
conversation about pkg_add, pkg_info, and default PKG_PATH.
I've learne
On Dec 09 16:58:16, glok...@kuzdra.org wrote:
> The FAQ page [FAQ15] suggests to use "pkg_info -Q" to search the
> collection of pre-compiled packages. When I search for "tcl",
> I get a few "nextcloud" packages only, but no Tcl:
>
> $ pkg_info -v -Q tcl
> PKG_PATH=
> nextcloud-27.1.11
On 12/9/24 7:58 AM, Maxim wrote:
The FAQ page [FAQ15] suggests to use "pkg_info -Q" to search the
collection of pre-compiled packages. When I search for "tcl",
I get a few "nextcloud" packages only, but no Tcl:
$ pkg_info -v -Q tcl
I've been using lynx instead:
lynx --dump https://cdn.op
The FAQ page [FAQ15] suggests to use "pkg_info -Q" to search the
collection of pre-compiled packages. When I search for "tcl",
I get a few "nextcloud" packages only, but no Tcl:
$ pkg_info -v -Q tcl
PKG_PATH=
nextcloud-27.1.11p0
nextcloud-28.0.11
nextcloud-28.0.12
nextcloud
6 matches
Mail list logo
