[MacPorts] #69739: input-leap @2.4.0-20231009: error: no viable conversion from returned value of type 'unique_ptr<inputleap::SecureSocket>' to function return type 'unique_ptr<inputleap::IDataSocket>'

[MacPorts]

#69739: input-leap @2.4.0-20231009: error: no viable conversion from returned value
of type 'unique_ptr<inputleap::SecureSocket>' to function return type
'unique_ptr<inputleap::IDataSocket>'
-------------------------+-------------------------------
  Reporter:  ryandesign  |      Owner:  Koston-0xDEADBEEF
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.9.3
Resolution:              |   Keywords:
      Port:  input-leap  |
-------------------------+-------------------------------

Comment (by Koston-0xDEADBEEF):

 Alright, port has been updated, build system is much cleaner now and I
 took a closer look at this.

 The bug is actually in OS X 10.11 SDK implementation of std::unique_ptr,
 which is a massive C++ template hell. I don't have enough sanity points
 (or time) to spend coming up with a reasonable solution for this, I'm
 afraid.

 On the bright side, input-leap development has picked up a bit recently
 and one of the goals is ensuring backwards compatibility with barrier and
 even old synergy. It's always been compatible with barrier, but now
 guaranteeing compatibility is an explicit goal.

 I suggest closing this ticket as "won't fix", instead encouraging OS X
 10.11 users to use barrier instead and ensuring it remains in the ports
 tree for this purpose.

-- 
Ticket URL: <https://trac.macports.org/ticket/69739#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS