From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 4 10:33:51 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DC01CEBA for ; Wed, 4 Dec 2013 10:33:51 +0000 (UTC) Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 700891564 for ; Wed, 4 Dec 2013 10:33:51 +0000 (UTC) Received: by mail-we0-f176.google.com with SMTP id w62so9001478wes.7 for ; Wed, 04 Dec 2013 02:33:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=q+qBxxC9SSUSNHca6tOmkE+LkdOExMMJEEmmnZ6jaDI=; b=lFaYw9+sXjb9yfz+j6v4MLtJtfhbDQ5HGHXNZoUOIT8G5bBKkaWAPFPoxtxuQHfuy3 I72QCOBkirf11HuqbcFPIU5SMbYUqHsulXf50CW3d7CXx839QKoH2VrgTiA29G7RFoi6 5JiVqLxd4VIEj54HHd4Z1HwdLfA60Lbf2B3/hJzhUTdb5Hetw/zRhE6FsJiINUbKN6sm TfLmzKPdd53OYeye3gVRuLS5asMC2Z78Sz0j+2OsMGczsdMBN9rtLeMD1j8J2jmiI9qU +1J89emLKPrSJ0ys6ND+wIdgK+Mj9DYskUP/cRwN+lnZ7E/Q+iK/rGWnivgFOtn9C3jU aasA== X-Received: by 10.180.39.177 with SMTP id q17mr6629877wik.16.1386153229624; Wed, 04 Dec 2013 02:33:49 -0800 (PST) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id f11sm5683819wic.4.2013.12.04.02.33.48 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 04 Dec 2013 02:33:48 -0800 (PST) Sender: Baptiste Daroussin Date: Wed, 4 Dec 2013 11:33:46 +0100 From: Baptiste Daroussin To: "freebsd-hackers@freebsd.org" Subject: Re: Who should really be using libbsdxml? Message-ID: <20131204103346.GS27759@ithaqua.etoilebsd.net> References: <20131204082331.GV14900@kiwi.coupleofllamas.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RvrrZ8vH9xW05bsQ" Content-Disposition: inline In-Reply-To: <20131204082331.GV14900@kiwi.coupleofllamas.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 10:33:51 -0000 --RvrrZ8vH9xW05bsQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 04, 2013 at 12:23:31AM -0800, R. Tyler Croy wrote: >=20 > I'm working on a daemon for FreeBSD specifically, which I hope to one day= merge > into the base system, but first is going to live in ports for some amount= of > time. >=20 > Does it make sense for me to even bother using libbsdxml right now, or sh= ould I > just reference and link against a ports-installed libexpat? Switching to libbsdxml would be easy if it one day goes into base, but for = now keep using libexpat, libbsdxml is not intended to be used outside of base. Even pkg(8) now uses a bundled version of expat to avoid using libbsdxml regards, Bapt --RvrrZ8vH9xW05bsQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlKfBQoACgkQ8kTtMUmk6Eym3QCePgZY92/sw0cABRCTFmPicToY voEAn21clEWJHDoCwgRiMNtWpGPK9vTu =cB3L -----END PGP SIGNATURE----- --RvrrZ8vH9xW05bsQ--