In D53051#1225647, @cperciva wrote:

This seems to have stalled; ok if I take it off the 15.0 issues list?

In D53491#1225645, @cperciva wrote:

This isn't intended to land in 15.0 any more, right?

In D53605#1223886, @jlduran wrote:

Perhaps the discussion can be if we want to make WITHOUT_BLOCKLIST the default? That would be understandable, since it has a low usage rate, I would approve that.

also update mtree

In D53605#1223871, @jlduran wrote:

Just to make sure I'm on the same page, because to me having FreeBSD-blocklist-lib and FreeBSD-blocklist would be like having FreeBSD-ssh and FreeBSD-ssh-lib.

fix the UPDATING text to match the use of LIB_PACKAGE

In D53484#1223366, @glebius wrote:

Note that there are tests that use routed :(

In D53576#1223087, @emaste wrote:

Will runtime need a dependency on libcasper now?

i don't know enough about ports to say if this is the right way to do this, but in principle disabling vulnerability checks here seems correct, otherwise building release would randomly break whenever VuXML is updated. which is, i suppose, what prompted this change in the first place.

while you're here, i notice there is some existing text in this page which is wrong:

i'm okay with this change but, based on what i remember of your original description of the problem, could explicitly installing FreeBSD-clibs-lib32 avoid it? or does it not actually require 32-bit libgcc at all?

thanks.

would you approve an MFH for this change? it's pretty straightforward and provides a useful feature.

PR: 289683

remove some wrongly added text

try this:

sorry for the delay: i see your point but i'm still not entirely comfortable with this change. are we sure that BSDINSTALL_PKG_REPOS_DIR will only contain the base repository? what if the repo dir already exists in the target and has other config files? (i'm not sure if this is a supported situation for bsdinstall pkgbase, but...)

In D53486#1221110, @cperciva wrote:

Yes, the code in usr.sbin/pkg should probably error out rather than quietly producing the wrong output, but I wasn't sure how best to do that (and we needed this fix anyway, not just better diagnostics).

you are in a maze of twisty little .ifs, all alike...

this is fixed in pkg 2.4.0: the directory is no longer recreated when upgrading the package.