Date: Sat, 6 May 2023 16:21:42 +0000 From: Arthur Chance <freebsd@qeng-ho.org> To: Yuri <yuri@aetern.org>, freebsd-questions@freebsd.org Subject: Re: Error in vm manpage Message-ID: <1a48dbcf-71ba-69a0-c010-f16b11d14628@qeng-ho.org> In-Reply-To: <4763e87b-86bb-8756-4d67-febc6c3d6b04@aetern.org> References: <2986dfd0-ac48-9793-f480-84c8e6f4d222@Gmail.com> <f1994bbd-0516-6cf5-13ff-74816bf1620d@qeng-ho.org> <4763e87b-86bb-8756-4d67-febc6c3d6b04@aetern.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/05/2023 15:56, Yuri wrote: > Arthur Chance wrote: >> On 06/05/2023 11:25, Steven Friedrich wrote: >>> In Windows Support section, it mentions uefi-edk2-bhyve port. >>> >>> No such port or package exists. >>> >>> >> >> It appears there are two versions >> >> sysutils/uefi-edk2-bhyve-csm > > This one is deprecated. > >> sysutils/uefi-edk2-bhyve-devel > > This one does not exist since 2021. > > Everything is now in sysutils/edk2 as flavors, e.g. package names will > currently be: > > edk2-bhyve-g202202_2 > edk2-fvp-g202202_2 > edk2-macchiatobin-g202202_2 > edk2-qemu-x64-g202202_2 > edk2-rpi3-g202202_2 > edk2-rpi4-g202202_2 > edk2-qemu-i386-g202202_2 > edk2-xen-x64-g202202_2 > Maybe it's time I regenerated my ports rather than just updating them. It would appear portsnap doesn't necessarily delete old ports as I have both ports on my system and my last portsnap update was just after midnight today. Also ports.freebsd.org doesn't seem to be up to date on these ports. -- We build our computer systems the way we build our cities; over time, without a plan, on top of ruins. — Ellen Ullman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1a48dbcf-71ba-69a0-c010-f16b11d14628>