Date: Fri, 14 Dec 2018 10:30:51 +0100 From: Mathieu Arnold <mat@FreeBSD.org> To: Romain =?utf-8?B?VGFydGnDqHJl?= <romain@freebsd.org> Cc: Jan Beich <jbeich@freebsd.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r487403 - head/databases/puppetdb-cli Message-ID: <20181214093051.stocdnar7vrhmark@atuin.in.mat.cc> In-Reply-To: <20181214070225.GA13003@blogreen.org> References: <201812140259.wBE2xbuT015992@repo.freebsd.org> <sgz0-u1l5-wny@FreeBSD.org> <20181214070225.GA13003@blogreen.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--32caxjjuk3wpeeqt Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 13, 2018 at 09:02:25PM -1000, Romain Tarti=E8re wrote: > On Fri, Dec 14, 2018 at 06:19:50AM +0100, Jan Beich wrote: > > Romain Tarti=E8re <romain@FreeBSD.org> writes: > >=20 > > > +BROKEN_SSL_REASON_libressl=3D Needs an old version of OpenSSL (older= than 1.1) > >=20 > > Does it build fine with DEFAULT_VERSIONS+=3Dlibressl-devel ? >=20 > Of course not, good catch! Probably the same for openssl-devel but it > seems absent as of today, so I don't know if we should add it. >=20 > > > +.include <bsd.port.pre.mk> > >=20 > > .include <bsd.port.options.mk> would have been enough. >=20 > Yes, it seems to be okay too. I was following > https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.h= tml#dads-after-port-mk >=20 > > > +.if ${OSVERSION} >=3D 1200085 > >=20 > > Checking OSVERSION without OPSYS is illegal. DragonFly has OSVERSION=3D= 9999999 > > with LibreSSL 2.4.4 in base. > >=20 > > https://github.com/DragonFlyBSD/DPorts/blob/f18014a15a13/Mk/bsd.port.mk= #L1184 > > https://github.com/DragonFlyBSD/DragonFlyBSD/blob/bd84e83893b2/crypto/l= ibressl/README.DRAGONFLY >=20 > Fixed! >=20 > > > +BROKEN_SSL+=3D base > >=20 > > BROKEN_SSL=3Dbase is *not supported* by USES=3Dssl, and BROKEN_SSL cann= ot set > > after bsd.port.pre.mk because USES=3Dssl was already processed by that = time. >=20 > D'oh! Maybe this information may have it's place in the Porter's Handboo= k: > https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.h= tml#uses-ssl No, the fact that it is not supported is a bug, but as nobody ever said it was not working, I only discovered it last week or something. --=20 Mathieu Arnold --32caxjjuk3wpeeqt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEEOraXidLtEhBkQLpbOkUW81GDzkgFAlwTeEtfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNB QjY5Nzg5RDJFRDEyMTA2NDQwQkE1QjNBNDUxNkYzNTE4M0NFNDgACgkQOkUW81GD zkhMxg/+MKAJgAtpuV8pNpkmRJfVUtj0pZQnUsSS5ohwKpsO6fJDxVfXU5et5YCY RIGw+X6yuNiW/R/9KjIlGwPtZtfV1/lh2oZXe01u9qk4aa85E/ZiNlt+enp6i7S1 N95gy2H5v8jmR8c1zaSCKLZH5byXvgUeQICA4sdiNy4bBQTDFIFVrNVW5k8VqBYI CWIFA+7vE8jij4nyM2Eh9k2+pnRSnyz16hKzKhcmxiJ/MMiRV/rmsm63G6GAz5fv RPaYHIqRV3JvYIuDUTqq0mFkePr2RLAngVkPkF7BgzugHBzVCq8JTOaV8ppkQ/vd vIJ1x3cZeFikD4WZGUEz97lRHBn2VF0tkaCnYKlio6FNsGTmTVsD2gwPlgTja+sQ JBWcNlTBNmyczyFiDGg43fV+AQq3BS6XOLp7ISNG7c+2HnL8QNHoQ0roYB6kcqXN LXDTpwNxbXoT8b/g6C1ej1IqwjfKEoyAMye8vybv46s8oadpn00Z1aCL+NG9LyIU VmFc7QpLjmyoJLQ5iC8j93yPatVyFpgKkrYQnV7YTkpW3vA9QZnfz635ULjTPWK6 AEbyXXGpOf8Yt+6WYhON1rSY6e6yTYOi0agvlJ+4mcazDIjsdcaxcNvjwOw0liIJ 0M6KdaqYMhQVEHwStkd/0vcX0hQCIV5k+XWN+vijc1GSRsaA9WU= =yvyh -----END PGP SIGNATURE----- --32caxjjuk3wpeeqt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181214093051.stocdnar7vrhmark>