net/wifi-firmware-kmod: add a release flavor

[bz]

Summary

Add a flavor of of which wireless firmware packages to put onto a
relase media. There is no point hsipping them for the installer
if there is no active driver for them yet.

Sponsored by: The FreeBSD Foundation

[lwhsu]

I think in the ports the convention is having "release" as default, and "devel" for the WIP. I feel it would be less confusing for the end users, what do you think? (and sorry for the bikeshedding.)

[bz]

In D47141#1074848, @lwhsu wrote:

I think in the ports the convention is having "release" as default, and "devel" for the WIP. I feel it would be less confusing for the end users, what do you think? (and sorry for the bikeshedding.)

The "default" name is internal and could be "foo" but comes from the Ports Handbook first example.
I don't want to change the name of the "base" port into -devel and I don't want a third flavour for devel really either. It's a meta-port to build all the others and should not be used by anyone.
fwget(8) will install the individual driver's firmware flavor (a single line from this port) for people.

[cperciva]

In D47141#1074848, @lwhsu wrote:

I think in the ports the convention is having "release" as default, and "devel" for the WIP. I feel it would be less confusing for the end users, what do you think? (and sorry for the bikeshedding.)

Note that "release" in the context of this patch means "version which goes onto FreeBSD release media", not "version which is released for users". Someone running -STABLE would not want the "release" version.

[bz]

This seems to do as expected on 14.1-R and main amd64 poudriere builds

[cperciva]

Do you want to have a single "release" flavour or would it be better to have "X.Y-release" flavours? The firmware we need for one release might not be the same as we need for another release.

[bz]

In D47141#1079894, @cperciva wrote:

Do you want to have a single "release" flavour or would it be better to have "X.Y-release" flavours? The firmware we need for one release might not be the same as we need for another release.

It's mostly the other drivers are not connected to the build/working yet, so there's no need to complicate things with them. I assume eventually the -release can go again but it's a hike until then.

[bz]

There's still one big question: @cperciva do I need to figure out how to get these into the Quarterly package set for the release media too?