From owner-freebsd-gnome@FreeBSD.ORG Thu Mar 11 14:26:24 2004 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6176B16A4CE for ; Thu, 11 Mar 2004 14:26:24 -0800 (PST) Received: from server.alexdupre.com (host245-49.pool8288.interbusiness.it [82.88.49.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DE4143D2D for ; Thu, 11 Mar 2004 14:26:21 -0800 (PST) (envelope-from ale@FreeBSD.org) Received: from FreeBSD.org (thunder.alexdupre.com [192.168.0.101]) by server.alexdupre.com (8.12.9p2/8.12.9) with ESMTP id i2BMQJBI001982 for ; Thu, 11 Mar 2004 23:26:19 +0100 (CET) (envelope-from ale@FreeBSD.org) Message-ID: <4050E78B.9050405@FreeBSD.org> Date: Thu, 11 Mar 2004 23:26:19 +0100 From: Alex Dupre User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: gnome@FreeBSD.org References: <4050B731.7090401@FreeBSD.org> <1079033927.769.36.camel@gyros> In-Reply-To: <1079033927.769.36.camel@gyros> X-Enigmail-Version: 0.83.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA2BE25EE0BFC3F62AA6B4788" Subject: Re: libxml2 and threads X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2004 22:26:24 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA2BE25EE0BFC3F62AA6B4788 Content-Type: multipart/mixed; boundary="------------040602030504040803050604" This is a multi-part message in MIME format. --------------040602030504040803050604 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Joe Marcus Clarke wrote: > Threads are not just for developers. Users that don't need PHP, or > other non-threaded libxml2 consumers may want them. Yes, you are right, what I means is that it should be clearer that enabling threads in libxml2 can lead to problems regarding other ports. Initially I thought to add a disclaimer in php, but it's not the only port suffering this issue. This is why I think it should be added in the libxml2 port (my previous patch surely was not the best, but it was only an 'input' for a better comment). If you think the other ports should deal with this issue, then I'll add a disclaimer to php. -- Alex Dupre --------------040602030504040803050604 Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="signature.asc" LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZlcnNpb246IEdudVBHIHYxLjIuMyAo TWluZ1czMikNCkNvbW1lbnQ6IFVzaW5nIEdudVBHIHdpdGggVGh1bmRlcmJpcmQgLSBodHRw Oi8vZW5pZ21haWwubW96ZGV2Lm9yZw0KDQppRDhEQlFGQVVPY25nUlhwMk01ZlZVMFJBbHJM QUtEVUtnR3FsVXFreFpCYlRFdVdMZjlHemg3dzdRQ2ZmM0ZrDQowSVV3ZFhXOGtpb1F0M2Zh eWNKVXdHVT0NCj1KY09pDQotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0NCg0K --------------040602030504040803050604-- --------------enigA2BE25EE0BFC3F62AA6B4788 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAUOeLgRXp2M5fVU0RAvTGAJ911Sat31nIxQt4ixtxwHI9g4PtCgCcC+hl 5nrwKeF03RuUVyCKH09aQ0Q= =uBlD -----END PGP SIGNATURE----- --------------enigA2BE25EE0BFC3F62AA6B4788--