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 1EXNUi-0003Jf-FG for garchives@archives.gentoo.org; Wed, 02 Nov 2005 18:37:56 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jA2Ian03007637; Wed, 2 Nov 2005 18:36:49 GMT Received: from www.suchdol.net (www.suchdol.net [82.208.33.2]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jA2IXkEr031500 for ; Wed, 2 Nov 2005 18:33:46 GMT Received: from slon.basa.dejvice.czf (slon.basa.dejvice.czf [10.18.6.61]) by www.suchdol.net (Postfix) with ESMTP id 5DD8ED8C for ; Wed, 2 Nov 2005 19:33:39 +0100 (CET) From: Jan =?utf-8?q?Kundr=C3=A1t?= Organization: Gentoo To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP ??: Critical News Reporting Date: Wed, 2 Nov 2005 19:33:37 +0100 User-Agent: KMail/1.8.1 References: <20051101015125.1cc45eb4@snowdrop.home> <200511012257.22527.jkt@gentoo.org> <20051101221635.1a53a258@snowdrop.home> In-Reply-To: <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; boundary="nextPart1709175.MIU9qk7DRa"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511021933.38078.jkt@gentoo.org> X-Archives-Salt: 904edb1a-75cc-453c-b53c-d8daa2eb82e3 X-Archives-Hash: abfe4a5b7cac33f5839d4f3e0c83440f --nextPart1709175.MIU9qk7DRa Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 01 of November 2005 23:16 Ciaran McCreesh wrote: > | How will it handle GLSAs then? [1] > > gentoolkit !=3D portage. To quote GLEP 14 [1]: "Once this tool is implemented and well tested it can be integrated into=20 portage." > | > It's not a question of "what's wrong with XML?". It's a question of > | > "what advantage would we gain by strapping a giant flapping wet > | > kipper to a bicycle?". > | > | Or (a little bit rephrased) "why should we stick with consistent file > | formats". > > Uh, you'd have to invent a load of new XML DTD stuff for this anyway. Nope. We can build on *existing* GLSA DTD and on *existing* code. The downs= ide=20 is that Portage integration could be slower (same case as with `glsa-check`= ,=20 AFAIK). > So you're not using a consistent file format at all, you're just using > a consistent unnecessary layer in the middle, which as a side effect > makes your files incompatible with every standard Unix tool ever > written. See below. > Using XML does not magically make things compatible. XML is just a > layer in the middle. Any tool processing XML files still has to worry > about however the DTD in question works. Just to clarify - I don't say that XML is The Best Way To Go (tm), I'm just= =20 pointing out another possibility of implementation which is *very* similar = to=20 the way GLSAs are processed.=20 GLSA already contains stuff for marking items as valid only for given syste= ms,=20 for "injecting" them etc. Why don't use existing code? Why duplication? Have a look at the XML source of any GLSA. > You think XML magically makes things compatible? Then I suggest you > write a GuieXML to Docbook conversion tool, and see how many thousand > lines of XSLT it takes. All XML does is move the conversion and parsing > problems to a different, more complex level. I'm not familiar with DocBook, but I doubt I'll need thousands of lines of= =20 code. [1] http://www.gentoo.org/proj/en/glep/glep-0014.html WKR, =2Djkt =2D-=20 cd /local/pub && more beer > /dev/mouth --nextPart1709175.MIU9qk7DRa Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBDaQaCamXfqERyJRcRAlAuAKCO+xtQdvYFwcYgG+DYQXtxqXIdqQCgi2yU VsP5S7lObds3oLbz3Yzs/Ak= =/cnP -----END PGP SIGNATURE----- --nextPart1709175.MIU9qk7DRa-- -- gentoo-dev@gentoo.org mailing list