From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 4 08:23:44 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DABAAA27 for ; Wed, 4 Dec 2013 08:23:44 +0000 (UTC) Received: from sanddollar.geekisp.com (sanddollar.geekisp.com [216.168.135.167]) by mx1.freebsd.org (Postfix) with SMTP id 6AE241D62 for ; Wed, 4 Dec 2013 08:23:44 +0000 (UTC) Received: (qmail 15370 invoked by uid 1003); 4 Dec 2013 08:23:37 -0000 Received: from unknown (HELO kiwi.coupleofllamas.com) (tyler@monkeypox.org@173.239.70.2) by mail.geekisp.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Dec 2013 08:23:37 -0000 Date: Wed, 4 Dec 2013 00:23:31 -0800 From: "R. Tyler Croy" To: "freebsd-hackers@freebsd.org" Subject: Who should really be using libbsdxml? Message-ID: <20131204082331.GV14900@kiwi.coupleofllamas.com> Mail-Followup-To: "freebsd-hackers@freebsd.org" MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="je0mZywpqEo4t1RU" Content-Disposition: inline User-Agent: Mutt/1.5.22 (2013-10-16) 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 08:23:44 -0000 --je0mZywpqEo4t1RU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. Does it make sense for me to even bother using libbsdxml right now, or should I just reference and link against a ports-installed libexpat? - R. Tyler Croy ------------------ Code: https://github.com/rtyler Chatter: https://twitter.com/agentdero rtyler@jabber.org --je0mZywpqEo4t1RU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlKe5oIACgkQFCbH3D9R4W//fACdGd6M4ZcBB/GO7C3ilc+1Pi+Z DdEAn0sdbFG+QgyMQmz3dtXB0Bw8sM9X =PPYr -----END PGP SIGNATURE----- --je0mZywpqEo4t1RU--