Date: Thu, 9 Apr 2015 01:59:00 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: John Wolfe <jlw@xinuos.com> Cc: freebsd-pkg@freebsd.org Subject: Re: Use of pkg plugins breaks the build of /usr/ports software Message-ID: <20150408235900.GK95321@ivaldir.etoilebsd.net> In-Reply-To: <55257B54.4050700@xinuos.com> References: <55257B54.4050700@xinuos.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150408235900.GK95321>