From owner-freebsd-pkg@FreeBSD.ORG Wed Apr 8 23:59:06 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D61615AE for ; Wed, 8 Apr 2015 23:59:06 +0000 (UTC) Received: from mail-vn0-x233.google.com (mail-vn0-x233.google.com [IPv6:2607:f8b0:400c:c0f::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85BE6D61 for ; Wed, 8 Apr 2015 23:59:06 +0000 (UTC) Received: by vnbg129 with SMTP id g129so18216526vnb.4 for ; Wed, 08 Apr 2015 16:59:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=1PKXpXwZlgb7WeZfMNmyzk1/eaZ4xg3cKsQHuPP8G5s=; b=PCJaQW9l52HG0dG2jnc8IS9X71QTs/YNPuk920Wepw7kNzSExKaOrzwJKWsXMdcuBC w9A/kVEHR5mEbpwuL208oBSS38TXI37QZyXRu4+02pY06oFS3b+wYvGMfKq0n3NNPiSt sYnvUIm3KXMW/iIt59srzA+3YmhiSTIqlKFNy238tlPEz9VKVsd/DRnwNKPwiVa6ePpq idx9mASeVmfj4oV36YD2n0mP2xP90wFD2hUQ1E8TDobi+dgREknS9h7ElfgD6LQK7y5Q sruftHAXSXrer9ENE6/9zT5gUjqsMHwggy2tDxHJ2sdEt1YRK/0sZvVvZslrwNy9nkpq O7lA== X-Received: by 10.52.143.233 with SMTP id sh9mr20153762vdb.26.1428537545366; Wed, 08 Apr 2015 16:59:05 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id p12sm2316689vds.23.2015.04.08.16.59.02 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Apr 2015 16:59:04 -0700 (PDT) Sender: Baptiste Daroussin Date: Thu, 9 Apr 2015 01:59:00 +0200 From: Baptiste Daroussin To: John Wolfe Subject: Re: Use of pkg plugins breaks the build of /usr/ports software Message-ID: <20150408235900.GK95321@ivaldir.etoilebsd.net> References: <55257B54.4050700@xinuos.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cEobB2knsyc5ebfU" Content-Disposition: inline In-Reply-To: <55257B54.4050700@xinuos.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2015 23:59:07 -0000 --cEobB2knsyc5ebfU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 08, 2015 at 03:02:44PM -0400, John Wolfe wrote: > Having built a pkg-plugin based on the pkg-plugin-template at=20 > https://github.com/freebsd/pkg-plugins and adding >=20 > > PLUGINS [ > > "x-adminsync", > > ] >=20 > the plugin is working as desired. Good so far...... >=20 > I was caught off guard when later attempting to "make" something in=20 > /usr/ports. The builds fail miserably with multiple >=20 > > pkg-static: Loading of plugin 'x-adminsync' failed: Service unavailable > > pkg-static: Plugins cannot be loaded > > make[1]: "/usr/ports/Mk/bsd.port.mk" line 1206: warning:=20 > > "/usr/local/sbin/pkg-static version -t 1.4.12 1.3.8" returned non-zero= =20 > > status >=20 > I would not expect that a static binary be able to load and use a=20 > relocatable object so I am surprised that it even tried to do so. Even=20 > so, a failure should be expected and not terminate the pkg-static process. >=20 > Is this a bug, works as designed? >=20 Hum probably both, I need to rework pkg-static so that it is not entierly s= tatic but static for all but libc so that it allows plugins, Haven't done that wo= rk yet. What bothers me is that pkg-static should not even tried to load plugins so= it should not return any failure, that is a bug, I'll try to see fix it. Btw I'm happy to see someone is actually using the plugin interface, I have= n't spent time on it since 1.3 and happy to see that I haven't broken it :) I would like to hear more feedback about the usage of plugins, how good/bad= it is, how we could improve it etc, this is the first time I'm coding a plugin interface I do not expect it so be good :) Best regards, Bapt --cEobB2knsyc5ebfU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlUlwMMACgkQ8kTtMUmk6EwAtwCgmN8QEW0XsK5vEnYlUQAxW9jg Vi4An1UlwYdvldfMHFX2toMk4jjnbYkc =4S/X -----END PGP SIGNATURE----- --cEobB2knsyc5ebfU--