From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#34927: Curl is not configured to use its dependency libssh2 Date: Thu, 21 Mar 2019 00:54:02 +0100 Message-ID: <87lg1985lx.fsf@fastmail.com> References: <20190320204052.GA21181@jasmine.lan> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:50007) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h6lFq-0000kv-1T for bug-guix@gnu.org; Wed, 20 Mar 2019 20:08:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h6l30-0006wC-Sg for bug-guix@gnu.org; Wed, 20 Mar 2019 19:55:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:38949) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h6l30-0006vX-AB for bug-guix@gnu.org; Wed, 20 Mar 2019 19:55:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h6l30-0006vT-1c for bug-guix@gnu.org; Wed, 20 Mar 2019 19:55:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190320204052.GA21181@jasmine.lan> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Leo Famulari , 34927@debbugs.gnu.org --=-=-= Content-Type: text/plain Leo Famulari writes: > While working on a libssh2 update [0] I noticed that curl was not > keeping a reference to libssh2, even though libssh2 is an input of the > curl build. > > Our curl package is missing the required configuration option: > > ------ > SSH support: no (--with-libssh2) > ------ > > I assume that our curl package did build with SSH support in the past, > but I'm not sure. > > It's unfortunate that we have to use a graft to update libssh2 even > though only a few dozen packages refer to it, because of this curl > issue. > > What should we do about curl? Should we remove libssh2 from its inputs, > or enable the build-time --with-libssh2 configuration option? Since no one apparently uses it, let's just remove it. I'm something of a curl power user and did not know it even had SSH support! In the mean time, if curl is the only "heavy" user of libssh2, we can give it a non-public or hidden libssh2 package that stays on version 1.8.0 to avoid the graft. WDYT? --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlyS0poACgkQoqBt8qM6 VPrp3gf+IuLN3BfIFCkpuJGO+Wno+XEV7NxxujkNMDSxt4/sKmWJ5uRg/xGH3JhK W2IVh9N1K38SKzzUlhmi/Ggw+BLelg6i0OcIwNW/hYyt/JLaBoKYtYI9Z9P5icsb yUsofojL2ezM1l0xvORpmAGRG3HuMaoeOSlUWK+o0MOPYNZ5dv9Xbp/PZl3M+0u2 AEMzWvV69owOjPs3hlAgtPMIv3dqkZhaBt1pOzSGIb4Ne1q8ABQInB1N81Gf2mg2 +WWgw7uj/39k3itj/gftRk2h+U12PIZpHCLQiqh28n9OYdAi+6kXuB26ABLQq+hy b9e8N799jWYSqL4sB331uriiaSKEUQ== =4/mn -----END PGP SIGNATURE----- --=-=-=--