> On 18 Aug 2020, at 11:29, O'Connor, Daniel wrote:
> I think it would make sense to patch the port to add another stanza which
> matches EFISYS as well as EFI.
>
> What do you think?
I was going to file a bug but bugzilla is having a nap right now.
This patch works for me:
[midget 12:47]
Hi Guido,
> On 8 Aug 2020, at 18:03, Guido Falsi via freebsd-stable
> wrote:
>>
>> i'm not sure if there's a more granular way to do this. Alternatively,
>> you could create a /boot/efi or /boot/msdos or similar and mount it at
>> boot so that xfce doesn't even try it. EFISYS = EFI System
> On 18 Aug 2020, at 11:23, O'Connor, Daniel wrote:
>
>> On 8 Aug 2020, at 18:03, Guido Falsi via freebsd-stable
>> wrote:
>> Hope this helps.
>
> Thanks for this, I got it working by specifying block.device (twice, once for
> /dev/msdosfs/EFISYS and once for /dev/gptid/). Is there a way
Eugene Grosbein writes:
> 14.08.2020 17:46, Bengt Ahlgren wrote:
>
>> Then the question is whether I need openssl libraries from ports, when I
>> use that for all ports with DEFAULT_VERSIONS+=ssl=openssl due to QT5
>> requirements?
>>
>> If I want to link with openssl from ports, it looks like
