Re: 12.0-RC1: unifi5 can't be installed due to mongodb34 build failure

Tested Kurt's suggestion. Built, installed okay, and looked working (days ago). But with some warning/error messages about dlopen-ing libcrypto. And pkg wanted to remove mongodb34 and unifi5 whenever I tried to install something. For Ronald's suggestion, unifi5(or any port maybe?) can't be built wi

Re: [pkg-fall...@freebsd.org: [package - head-amd64-default][security/tcpcrypt] Failed for tcpcrypt-0.3.r1 in build]

It is the question if this port is not deprecated. https://github.com/sorbo/tcpcrypt => Latest commit b2673e8 on Jul 24, 2014 ___ freebsd-ports@freebsd.org mailing

[pkg-fall...@freebsd.org: [package - head-amd64-default][security/tcpcrypt] Failed for tcpcrypt-0.3.r1 in build]

It looks like the recent import of OpenSSL broke this port. What is the best way to handle this? Is there a way to mark this port and using the old version? or? Please include me in the reply, as I don't receive emails from the list, only subscribed to send this. Thanks. - Forwarded messag

Re: Best way to generate a patch file

Dan Mahoney (Gushi) wrote: > All, > > I'm requesting takeover of a couple of FreeBSD ports (cvs and dma, > although dma is now in base, I imagine the port will be used to track > upstream changes before they make it into base). > > What has been requested thusfar is a diff to update maintainer. 

Best way to generate a patch file

All, I'm requesting takeover of a couple of FreeBSD ports (cvs and dma, although dma is now in base, I imagine the port will be used to track upstream changes before they make it into base). What has been requested thusfar is a diff to update maintainer. Seems simple enough, right, effectiv

Maia Mailgaurd

Hi Janky Jay, Can I ask if you there are any plans to patch Maia so it can run on php70+? Many thanks for the great port. -- Regards, Gary J. Hayers g...@hayers.org PGP Signature https://www.hayers.org/pgp ___ freebsd-ports@freebsd.org mailing list

Re: ssl=base

25.11.2018 18:57, Franco Fichtner wrote: >> Why can't you use LibreSSL port for some ports and base libssl for other >> ports? >> That is, net/mpd5 links with base system libfetch that depends on base >> libssl, >> so it is example of port that cannot be built with LibreSSL. > > FWIW, since 201

Re: ssl=base

I had this problem in the past, the solution I found was to build a "port" of libfetch using /usr/src/lib/libfetch link libfetchagainst security/openssl and than net/mpd5 against the libfetch in /usr/local/lib It was some time ago.. ___ freebsd-ports@f

Re: ssl=base

> On 25. Nov 2018, at 12:51 PM, Eugene Grosbein wrote: > > Why can't you use LibreSSL port for some ports and base libssl for other > ports? > That is, net/mpd5 links with base system libfetch that depends on base libssl, > so it is example of port that cannot be built with LibreSSL. FWIW, si

Re: ssl=base

25.11.2018 18:46, Mathieu Arnold wrote: >> As maintainer of the net/mpd5 port, I wonder why our ports/Mk/Uses/ssl.mk >> prevents building this port using FreeBSD 12 and base system libssl >> when libressl is installed? >> >> While building with ssl=base, the port itself does not include headers >>

Re: ssl=base

On Sun, Nov 25, 2018 at 03:12:43PM +0700, Eugene Grosbein wrote: > Hi! > > As maintainer of the net/mpd5 port, I wonder why our ports/Mk/Uses/ssl.mk > prevents building this port using FreeBSD 12 and base system libssl > when libressl is installed? > > While building with ssl=base, the port itsel

ssl=base

Hi! As maintainer of the net/mpd5 port, I wonder why our ports/Mk/Uses/ssl.mk prevents building this port using FreeBSD 12 and base system libssl when libressl is installed? While building with ssl=base, the port itself does not include headers from ${LOCALBASE}/include and it does not include ${