Hi. If the configure script don't pick up on extra features and libraries on its own, I would maintain my own version of the port in /usr/ports/mine or similar. Custom ports should be listed by ports -d when the installed version of the port is older than what can be find in core/opt/contrib. -- Joacim <hi@joac.im> On Mon, 2022-06-20 at 21:25 +0200, Martin Michel wrote:
Hi there,
I wonder how you long-time CRUXers handle the case if a package from core/opt/xorg/contrib port does not suit your needs?
I read it is discouraged to create duplicate (local) packages but alternatives like installing local builds directly in /usr/local, /opt or ~/.local seem also suboptimal.
For example, I need sftp support in libcurl which needs linking against libssh. This is not configured in the official port. So I have to create my own solution and I want it to integrate as smooth as possible with the ports systems and keep CRUX's philosophy. What do you recommend?
Thanks for your input!
Best regards, Martin _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux