Case in question is, once again, multimedia/makemkv.For a long time, the distfiles contained binaries of the closed-source part for amd64 and i386 only, so naturally, the port had ONLY_FOR_ARCHS= amd64 i386 Now, upstream started adding binaries for armv7 and aarch64. From these, Linuxulator is only available on aarch64. Therefore the variable now looks like this: ONLY_FOR_ARCHS= aarch64 amd64 i386 This is, of course, exactly the default that USES=linux would set anyways. Now I'm unsure whether I should just drop it and go with the default? Pro: It's actually the availability of Linuxulator that results in the narrowest restriction now. Con: The upstream software *is* restricted regarding ARCHs and maybe this should stay being reflected. What would you think is the better way to go?
There is work underway to port the linuxulator to other architecture(s). I would suggest to keep the ONLY_FOR_ARCHS in the port.
Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netch...@freebsd.org : PGP 0x8F31830F9F2772BF
pgpKVKpsUr_Z4.pgp
Description: Digitale PGP-Signatur
