Minor version change of dependency causes major differences in pkg-plist

[krasenyp]

I ported an Elixir service which has a build dependency erlang_runtime26>=26.0. The problem is that on every minor version change of the dependency, I need to generate a new pkg-plist file because directory erts-13.2.2.4 is replaced by erts-14.0.0.2. There are around 10 directories which get replaced, with dozens of files. Is there a better way to manage pkg-plist in this situation?

 

[T-Aoki]

Maybe x11/linux-nvidia-libs could be a hint.

Ports has a mechanism to replace something like %%VarName%% in pkg-plist with the value of variable VarName in its Makefile.

See x11/linux-nvidia-libs/Makefile and x11/linux-nvidia-libs/pkg-plist for an example. Especially about SHLIB_VERSION.

 

[krasenyp]

Thank you! I think I found a, probably not optimal but working, solution - TMPPLIST. If someone needs inspiration to do the same, it can be found in java/eclipse's Makefile.

 

[T-Aoki]

Ah, x11/linux-nvidia-libs/Makefile has a bunch of ${TMPPLIST} operations, too.

For simple version replacements, %%VarName%% method is used.
But for more complicated cases such as "this file is only available versions before x" cases, ${TMPPLIST} method, which removes unneeded lines/portions of lines using ${REINPLACE_CMD}, are used. So it's complicated to understand. But supports many legacy versions with single Makefile as master port.