Date: Wed, 3 Nov 2010 11:27:27 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Iain Hibbert <plunky@rya-online.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp should not use libbsdxml Message-ID: <AANLkTimSwFNjEBR55498Re66zAxujhY4hJmcZc77eKwM@mail.gmail.com> In-Reply-To: <alpine.NEB.2.00.1011031008260.1738@galant.ukfsn.org> References: <alpine.NEB.2.00.1011031008260.1738@galant.ukfsn.org>
index | next in thread | previous in thread | raw e-mail
On Wed, Nov 3, 2010 at 3:27 AM, Iain Hibbert <plunky@rya-online.net> wrote: > Hi, > > according to the libbsdxml manpage, > > http://www.freebsd.org/cgi/man.cgi?query=libbsdxml&apropos=0&sektion=0&manpath=FreeBSD+8.1-RELEASE&format=html > > it should not really be used by external programs.. using expat directly > (as per patch below) will cut down on a patch that is required on NetBSD > > + expat dependency would need to be added in ports/comms/obexapp > (I guess that translating expat to builtin bsdxml could feature > automatically in ports framework using ln -s) thanks for the patch (again :) i'm not entirely sure about this one. i usually really dislike adding extra dependencies. because you never know what else it would drag. especially in case where everything is built from sources. i think, in this case, i could probably make an exception. these days libexpat is pulled with pretty much anything. so i guess it really probably not that big of a deal. ideally, i'd really want to get rid of openobex library and just put obexapp into base system (where it belongs imo). thanks, maxhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimSwFNjEBR55498Re66zAxujhY4hJmcZc77eKwM>