On Thu, 03 Nov 2005 19:29:45 -0500 "Nathan L. Adams" <[EMAIL PROTECTED]>
wrote:
| Flat files can be great in certain situations. Flat files do indeed
| make the parsing trivial. However SIMPLE CODE ISN'T ALWAYS THE MOST
| IMPORTANT REQUIREMENT. In the case of this GLEP, the most important
| requirement is getting the proper migration info to the users in the
| best possible way.

Read the list of requirements in the GLEP. The plain text solution
meets all of them. XML fails on several.

And, incidentally, I came up with the requirements list *before*
dismissing XML.

| So what are the trade-offs of the 'flat file'? If you store a
| migration guide as a 'flat file', its not going to be very readable.

Who said anything about storing a migration guide as a flat file? Read
the GLEP.

| GuideXML is the standard for Gentoo docs for some damn good reasons!

No, it's the standard because Daniel said so. And the reasons behind
which web publishing setup we use have little relation to good reasons
for a news delivery system.

Why do you think we still send email in plain text?

*shrug* Anyway, if you want to come up with an alternate GLEP based
around XML, bittorrent, Java and CORBA, go right ahead. The GLEP system
is quite happy with handling multiple competing proposals for a given
topic, and at the end of it we can select the best proposal, reject all
the proposals or go and come up with a new proposal with bits from
both.

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm

Attachment: pgpqfy2av9otm.pgp
Description: PGP signature

Reply via email to