Where is PKG_PATH stored

[scottro]

I've duplicated this experience a few times. If I use the install59.fs from nycbug.org, and, during installation, use the ethernet connect, afterwards, PKG_PATH is set to nycbug's mirror. If I choose to not configure a network card during installation, it's not set, and I do it manually afterwards, like normal people.

By set to, I mean that after I boot up the new system, I can just do pkg_add whatever without having to manually set a package path.


However, what I'm wondering, is where is PKG_PATH being set. I can't find it in my .profile or root's, nor in /etc/pkg.conf. Not a big issue of course, but I'm just curious where else the variable gets set, and a few minutes of googling didn't help. I also tried grep -r -i pkg in /etc/ but that didn't help either.

I wonder if it's just something nycbug does with their image, but figured I'd ask here first.

[jggimi]

If you install filesets from the network, the installer will create a pkg.conf(5) file for you. If you install from media, the installer will not create the file.

The file will be used if the $PKG_PATH environment variable is not set, so that you can use the variable to override the configuration file.

There is an /etc/examples/pkg.conf file available, also.

[scottro]

No, there is no pkg.conf file created. I am using an installf59.fs file, burned to USB. It's provided by nycbug.org, and if I choose defaults, will use their mirrors.

Again, unimportant question, it is just that I had expected an /etc/pkg.conf but there wasn't one.

[jggimi]

Let me restate, since you are using "install59.fs" from an official mirror.

OpenBSD is installed using the RAMDISK kernel (bsd.rd), which may be booted from a variety of media: diskette, optical drive, disk drive, or network. The options available depend upon the architecture.

In this case, the media you selected and put on USB is a disk-drive image containing both the bootable RAMDISK kernel, and all installable kernels and filesets. The only difference between the install59.fs image and the miniroot59.fs image is that the latter does not have any installable kernels or filesets.

No matter what media type you chose to use, or which variant you boot, the same bsd.rd kernel and the same script is used.

During install, you will be asked where the kernels and filesets for installation are located. They may be on local media, or they may be at a network location.

• If you select a network location for kernels and filesets, you will have a pkg.conf file created for you.
• If you select local media for kernels and filesets, you will not have a pkg.conf file created.

[jggimi]

Here are two excerpts from /usr/src/distrib/miniroot/install.sub for OpenBSD 5.9:

	# Bake a package path only if we installed from a mirror.
	PACKAGE_PATH=
	if [[ -n $_mirror ]]; then
		PACKAGE_PATH=$(print -r -- "$_url_base" |
			sed -E "/\/(snapshots|[0-9]\.[0-9])\/($ARCH)\/*$/!d
				s!!/%c/packages/%a/!;q")
	fi
.
.
.
	# Create or update pkg.conf with the new package path, if any.
	if [[ -n $PACKAGE_PATH ]]; then
		grep -v '^[ 	]*installpath[ 	]*=' /mnt/etc/pkg.conf 2>/dev/null >/tmp/pkgconf
		print -r -- "installpath = $PACKAGE_PATH" >>/tmp/pkgconf
		cp /tmp/pkgconf /mnt/etc/pkg.conf
	fi

The network location must be an official mirror. Installing from a private server will be treated like local media.

[scottro]

Ah, by golly, so it is. Ok, I think I missed it first time around, but I see now, on the install, a created /etc/pkg.conf

Thanks.

[bsd-keith]

When I install, I normally set it manually, by echoing it to my root .profile, & everything works.
Should I not do so?

[jggimi]

Entirely up to you, Keith, depending on how you want to manage your package install path.

(I use pkg.conf, and override with $PKG_PATH when/if necessary.)

[bsd-keith]

Thanks for confirming.