From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1EX6hq-0005wo-0p for garchives@archives.gentoo.org; Wed, 02 Nov 2005 00:42:22 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jA20ewS9025663; Wed, 2 Nov 2005 00:40:58 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jA20c33c028559 for ; Wed, 2 Nov 2005 00:38:07 GMT Received: from cpe-65-26-255-237.wi.res.rr.com ([65.26.255.237] helo=nightcrawler) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1EX6Vt-0003Qz-SA for gentoo-dev@lists.gentoo.org; Wed, 02 Nov 2005 00:30:01 +0000 Date: Tue, 1 Nov 2005 19:29:59 -0600 From: Brian Harring To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP ??: Critical News Reporting Message-ID: <20051102012959.GA16594@nightcrawler> References: <20051101015125.1cc45eb4@snowdrop.home> <200511011722.29840.jkt@gentoo.org> <20051101182506.4dd701f6@snowdrop.home> <200511012257.22527.jkt@gentoo.org> <20051101221635.1a53a258@snowdrop.home> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline In-Reply-To: <20051101221635.1a53a258@snowdrop.home> User-Agent: Mutt/1.5.8i X-Archives-Salt: 10f9cec1-94c4-42bf-b91d-8c00fbd23a96 X-Archives-Hash: 387abf323f717e9399544928431325f2 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset="en_US.UTF-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 01, 2005 at 10:16:35PM +0000, Ciaran McCreesh wrote: > On Tue, 1 Nov 2005 22:57:13 +0100 Jan Kundr=C3=A1t wrote: > | On Tuesday 01 of November 2005 19:25 Ciaran McCreesh wrote: > | > On Tue, 1 Nov 2005 17:22:29 +0100 Jan Kundr=C3=A1t > | > wrote: > | > | What's wrong with XML format similar to the one that is used for > | > | our GLSAs? > | > > | > 1. Portage does not handle XML. Portage will not handle XML in the > | > near future. > |=20 > | How will it handle GLSAs then? [1] >=20 > gentoolkit !=3D portage. Correct. Course, also incorrect. We already have a module for parsing metadata.xml in use in the=20 experimental 2.1 branch (which can be backported to 2.0 if anyone=20 wants it and does the work). Python comes bundled with xml as long as you don't have the build flag=20 enabled. > | > 5. XML is merely adding another problem to the one we have already. > |=20 > | Could you please explain? >=20 > Parsing XML is complicated. Writing XML is complicated. I put together > a complete working client that can show news items in the plain text > format proposed -- it took me fifteen minutes to write. I threw > together a script which can be called after a cron sync that mails news > items to root in under a minute. There is no way this could be done if > XML were being used -- any task involving news items would be a major > chore. Come on now, this is a bit of bullshit. http://dev.gentoo.org/~ferringb/portage_metadata.py, 47 lines Might be a pain in the ass under the frameworks you deal in, but=20 something as simple as news items can be done pretty quickly. > | > I have an eselect module which can read these news files. The whole > | > thing is about the same size as the DTD would need to be for an > | > XML-based solution. I have a parser written for the format in > | > question. The whole thing is smaller than the initialisation code > | > for an off the shelf XML parser. > |=20 > | Great. Why haven't you just used existing code from `glsa-check`, BTW? >=20 > Because merely figuring out the XML DTD takes longer than it does to > write an entire client for plain text news items. Not arguing for, or against, just pointing out certain arguements are=20 questionable... ~harring --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDaBaXvdBxRoA3VU0RApmkAJsGfKOJaRt6P3WfAKG4bPRNbFR/CACeKvlx nTYMr1ECNZ0SOD9OUUQOYQ8= =JAYx -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH-- -- gentoo-dev@gentoo.org mailing list