From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19378 invoked from network); 21 Jul 2004 13:43:07 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 21 Jul 2004 13:43:07 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BnHNC-0001Oi-KD for arch-gentoo-dev@lists.gentoo.org; Wed, 21 Jul 2004 13:43:06 +0000 Received: (qmail 15322 invoked by uid 89); 21 Jul 2004 13:43:05 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 17570 invoked from network); 21 Jul 2004 13:43:05 +0000 Date: Wed, 21 Jul 2004 07:43:01 -0600 (MDT) From: Jason Wever To: gentoo-dev@lists.gentoo.org In-Reply-To: <200407211415.49115.stuart@gentoo.org> Message-ID: References: <20040720131405.GW18023@mail.lieber.org> <200407211340.03982.stuart@gentoo.org> <200407211358.45806.tdickenson@devmail.geminidataloggers.co.uk> <200407211415.49115.stuart@gentoo.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [gentoo-dev] Revisiting GLEP 19 X-Archives-Salt: 7f3f9b3c-aeaf-4a05-a835-45adee4ecf0f X-Archives-Hash: 6f7a00c4c3ecc40ec8e4204f7d7271c9 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 21 Jul 2004, Stuart Herbert wrote: > On Wednesday 21 July 2004 13:58, Toby Dickenson wrote: > > No need for imagination here.... you can do much of that today with: > > > > emerge --changelog -p -u world > > An XML-based ChangeLog adds semantic meaning, making it much more useful. > It's not too difficult for (most ;-) humans to make sense of our current > ChangeLogs, but tools are always going to be limited in accuracy and > capability. > > There's also the added side-effect that it would make validating the ChangeLog > very straight forward through a simple XML Schema. I personally would very much like to leave ChangeLogs as they are. We already have tools to make sure they are in the right format (though repoman doesn't check for it and yes developers can choose not to use these tools). I think changing them over to XML would be more overhead in file size and in required tools to parse them than is really necessary. If the problem is that people can't follow directions, then don't punish those of us who do. Additionally XML is not (despite what many developers may think) easily human readable to those who don't understand how markup languages generically work. And even to some of us that know how, it's still (for lack of a better phrase) a royal PITA. While if this was solely a community of developers or technically savvy people, then perhaps using XML-based ChangeLogs would be OK. However it isn't and I think that would be a poor assumption on our part. Yes you could make a tool to make it human readable, but again that's more overhead you do not need if you can get developers to correctly input their ChangeLog entries now. Considering the file "ChangeLog" in an of itself is almost an unofficial standard that assumes a plain text document, should such a decision be made to go with XML-based ChangeLogs, perhaps we should give them another name. But yeah, that's my $0.02/rant 'n' rave. - -- Jason Wever Gentoo/Sparc Co-Team Lead -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD4DBQFA/nLndKvgdVioq28RAstZAJi6VfQX34lTgrfDsoEbU+x2c6kOAKCX80DK jg9FctPiw7OSTQzLHCVMxQ== =7BAm -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list