[macports-base] rev-upgrade complains for weakly linked dependencies

[Jason Liu]

Aha, I figured someone else would have encountered a similar situation and
filed a ticket already, but my searches in Trac weren't coming up with
anything. Since the ticket is already 7 years old, I guess that means that
it won't be getting fixed any time soon, so I guess I'll just have to use
the hack I alluded to in my original message.

-- 
Jason Liu


On Mon, Oct 16, 2023 at 6:04 PM <chrischavez at gmx.us> wrote:

> On 10/16/23 at 1:14 PM, Jason Liu wrote:
>
> > Hi all,
> >
> > I'm getting complaints from rev-upgrade for a library binary that is
> weakly
> > linked to a system framework which does exist on newer versions of macOS,
> > but doesn't exist on older macOSes. rev-upgrade thinks that it's a broken
> > file, and offers to rebuild the port; but of course rebuilding the port
> > won't do any good, because the system framework doesn't exist. In
> addition,
> > it's a bit difficult to simply remove the weak linking, because this
> piece
> > of the library is distributed as a pre-compiled binary blob by the
> upstream
> > devs, so it's not like I could modify some source code or CMakeLists
> file.
> > Is this something that could be fixed in macports-base, so that
> rev-upgrade
> > doesn't complain if a weakly linked dependency doesn't exist? (I could
> file
> > a Trac ticket if anyone thinks it's something worth pursuing.)
>
>
> I believe the ticket for this issue is
> https://trac.macports.org/ticket/52700
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20231016/4a66821f/attachment.htm>