Sorry, I completely forgot about this patch. Thanks for the ping.

In D52581#1256002, @bz wrote:

I assume the release-dvd.conf will need to change repos then in the release branch but that's a re@ task?

In D52581#1255798, @bz wrote:

I do not understand our package repositories and what goes into the releases anymore.
There's two branches in ports: main and quarterly; quarterly is almost certainly always outdated but I do not know how the "kmod" ports are dealt with in terms for that.
Is there one-repo-fits both main and quarterly or are they separate and we are building the full matrix?

@bz @bapt I think you're more familiar with the whole "release-specific kmod builds" thing than anyone else -- can you take a look at this? I don't want to ship the 14.4-RELEASE dvd with wifi kmods from 14.3.

Rebase to latest main

In D54542#1250514, @emaste wrote:

I want to make sure all the issues are fixed there before anything gets MFCed.

My preference is for all of the release building changes to be merged to stable/15, but after a significant amount of time & testing in main. Perhaps after the 14.4 process is complete?

In D54542#1250350, @ivy wrote:

are there any objections to landing this? i'd like to get started on multiple kernel support for bsdinstall, and it would be easier to get the other release changes in first.

In D54179#1245798, @emaste wrote:

@cperciva any suggestion on the best way to test this / confirm that I haven't missed something?

This code looks correct to me, but I'm not an expert in these bits so it would be great if @manu or someone else with arm64 experience can review.

Thanks, this fixes the issue I was seeing.

Ok, I'm going to have to refresh my memory of how these bits work.

Hmm, I thought the way this worked was that env_setup set defaults and then the config file was sourced to override those values.

Thanks, I'll leave the review up for a few more days in case anyone from re@ has comments but I'll make sure I commit it before the end of the month.

Fix typos

I think in 16.0 we won't be shipping distsets at all, so this menu will go away. But I agree with changing the wording but keeping the menu as an MFCable first step. Ideally I'd like to call distsets "legacy" in 15.1.

In D54035#1234772, @ifreund_freebsdfoundation.org wrote:

Oh, I see now that I assumed bsdinstall now uses /etc/pkg/FreeBSD.conf and overlooked the repos_dir = "/usr/share/bsdinstall/" line.

Why do we not use /etc/pkg/FreeBSD.conf for bsdinstall? I'm not seeing a case where the configuration for the FreeBSD-base repository there is different and it would be nice to get rid of the duplication if it is infact unnecessary.

We still want this for the install images.

In D53976#1234085, @dch wrote:

Updated all but the`pkg add -f ..` bit. I hear what you're saying @cperciva but I have already encountered test users who are not comfortable with git, and I would like to give them a simple alternative with mostly familiar tools.

Alternatively I could expand it out, make an explicit sha256 -c , and provide the actual file hashes in the document?

In D53964#1233037, @bdrewery wrote:

In D53964#1232996, @philip wrote:

We could probably shave off several seconds for many people by replacing pkg+https with pkg+http. The TLS n-way handshake is a complete waste of time. I have made this observation about the other repositories as well but...

Windmills. Have to keep trying.

Agreed. All https buys us here is quieting an FAQ. It otherwise adds time and potentially has problems in some corporate setups.

LGTM

@des Please commit this and MFC to stable/15 ASAP so I can get it into 15.0-RC4 builds on Monday.