On Sat, Mar 02 2019, Bruno Dantas <[email protected]> wrote: > I'm running 6.4-stable amd64 on my laptop. I have a repository on my > webserver where I keep custom packages (pardon the "gnuser" in url--the > domain predates my openbsd conversion). Accessing the repository > requires https, username, and password. Setting TRUSTED_PKG_PATH to my > repository has no effect, forcing me to use PKG_PATH and sign my own > packages. Observe: > > # cat /etc/installurl > https://cdn.openbsd.org/pub/OpenBSD > > # > TRUSTED_PKG_PATH=https://bruno:[email protected]/openbsd-custom/6.4/packages/amd64 > # PKG_PATH='' > # pkg_add myscripts > Can't find myscripts > > # TRUSTED_PKG_PATH='' > # > PKG_PATH=https://bruno:[email protected]/openbsd-custom/6.4/packages/amd64 > # pkg_add myscripts > myscripts-1.0: ok
TRUSTED_PKG_PATH and PKG_PATH won't have any effect unless they are exported in pkg_add's environment. Looks like in your case PKG_PATH is exported but TRUSTED_PKG_PATH isn't. Use either export var=value or env var=value pkg_add ... > I searched the mailing list for "TRUSTED_PKG_PATH" and didn't find > anything like this described. Did I find a bug? I doubt that. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
