From owner-freebsd-ruby@freebsd.org Fri Jun 30 19:36:00 2017 Return-Path: Delivered-To: freebsd-ruby@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 231A0D991EF for ; Fri, 30 Jun 2017 19:36:00 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id E8ED97A282 for ; Fri, 30 Jun 2017 19:35:59 +0000 (UTC) (envelope-from idefix@fechner.net) Received: by mailman.ysv.freebsd.org (Postfix) id E51E5D991EE; Fri, 30 Jun 2017 19:35:59 +0000 (UTC) Delivered-To: ruby@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E150BD991ED for ; Fri, 30 Jun 2017 19:35:59 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [IPv6:2001:608:a02::33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D60F7A281; Fri, 30 Jun 2017 19:35:59 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (aftr-88-217-181-97.dynamic.mnet-online.de [88.217.181.97]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id 21FE5C1AD0D; Fri, 30 Jun 2017 21:35:56 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1498851356; bh=s2cjikg1eyqQoFdciZd8jRaauwwl2yPrmHpTBDq+Gfc=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=JT35YhVpOFvCreh3Y7gvqUvs38J3HKE9ICs47rDcEp1nh0Prz+PgsHGosOMV7/b2v i8zubp5/9RS+j7/1lajP/pJCbFCVibKzELwyd1WFqwvVQ6nvtdbwLFsJPTN5xUNFX7 aGDT8MMg07y0LIql7DeoirQ8ANVe9kVBEuJaXCyQ= Received: from [192.168.0.151] (aftr-88-217-181-97.dynamic.mnet-online.de [88.217.181.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id 0E717CA7F3F; Fri, 30 Jun 2017 21:35:54 +0200 (CEST) Subject: Re: Help needed: net/rubygem-grpc To: Steve Wills , v@fatpipi.com Cc: Torsten Zuehlsdorff , ruby@freebsd.org, "Vanilla I. Shu" , Mathieu Arnold References: <4474b97e-88ec-ead8-bb13-79e5889bf237@FreeBSD.org> <2369ae1e-30cb-52d7-6697-a99139d74479@mouf.net> <029a9c1f-de69-3bfd-ff89-1a02feb767a0@fechner.net> <412f42ff-e5e7-03e8-fcbd-10d86d0c072c@mouf.net> From: Matthias Fechner Message-ID: Date: Fri, 30 Jun 2017 21:35:25 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nSiepe9AxnnelAVwTaIR82PWWvN3twAXj" X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jun 2017 19:36:00 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --nSiepe9AxnnelAVwTaIR82PWWvN3twAXj Content-Type: multipart/mixed; boundary="J0T9V6xX98fmm44kOGrXcB5Sd2xkEEGJn"; protected-headers="v1" From: Matthias Fechner To: Steve Wills , v@fatpipi.com Cc: Torsten Zuehlsdorff , ruby@freebsd.org, "Vanilla I. Shu" , Mathieu Arnold Message-ID: Subject: Re: Help needed: net/rubygem-grpc References: <4474b97e-88ec-ead8-bb13-79e5889bf237@FreeBSD.org> <2369ae1e-30cb-52d7-6697-a99139d74479@mouf.net> <029a9c1f-de69-3bfd-ff89-1a02feb767a0@fechner.net> <412f42ff-e5e7-03e8-fcbd-10d86d0c072c@mouf.net> In-Reply-To: --J0T9V6xX98fmm44kOGrXcB5Sd2xkEEGJn Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Am 30.06.2017 um 16:53 schrieb Steve Wills: > We can test rubygem-grpc 1.4.1, but as long as devel/grpc is using the > bundled boringssl instead of the one from the security/boringssl port, > rubygem-grpc might as well use it's bundled copy of boringssl. > > I was really hoping to avoid that as I really think bundling libs is a > bad idea in general and not something we should do. That's why I create= d > the boringssl port. > > Would you mind telling me why you didn't want to take that part of the > change to grpc? I don't mean to sound critical, of course. I may even > decide I agree with you, but I can't until I know the reasoning. :) > > Also, for the record, the boringssl port has potential to cause some > issues. Mathieu has agreed to look into fixing them. Copying him so he > can reply if his changes to boringssl require changes to the versions o= f > grpc and rubygem-grpc ports that link against the shared boringssl. Thank you all for your support. I finished today some other required rubygem ports which are required for gitlab 9.1. I was now able to build gitlab 9.1 with all dependencies. The current ports snapshot can be found here: http://gitlab.toco-domains.de/FreeBSD/GitLab/tree/9.1 Buildlogs here: https://pkg.fechner.net/index.html I will try to upgrade tomorrow a gitlab installation with these package to version 9.1, to see if the new version works. But how to test gitaly (which requires rubygem-grpc) is not clear for me. I have to do some rtfm here ;) Gru=C3=9F Matthias --=20 "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook --J0T9V6xX98fmm44kOGrXcB5Sd2xkEEGJn-- --nSiepe9AxnnelAVwTaIR82PWWvN3twAXj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAllWqBgACgkQkZS/qRt1bvYy2wCgysdqhl+GACxgXh+4LdLu7ytR XTIAoMtuJpR7V4KGqhDF/VU7nfvTxnZY =DCiK -----END PGP SIGNATURE----- --nSiepe9AxnnelAVwTaIR82PWWvN3twAXj--