1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Wed, 21 Jul 2004, Stuart Herbert wrote: |
5 |
|
6 |
> On Wednesday 21 July 2004 13:58, Toby Dickenson wrote: |
7 |
> > No need for imagination here.... you can do much of that today with: |
8 |
> > |
9 |
> > emerge --changelog -p -u world |
10 |
> |
11 |
> An XML-based ChangeLog adds semantic meaning, making it much more useful. |
12 |
> It's not too difficult for (most ;-) humans to make sense of our current |
13 |
> ChangeLogs, but tools are always going to be limited in accuracy and |
14 |
> capability. |
15 |
> |
16 |
> There's also the added side-effect that it would make validating the ChangeLog |
17 |
> very straight forward through a simple XML Schema. |
18 |
|
19 |
I personally would very much like to leave ChangeLogs as they are. We |
20 |
already have tools to make sure they are in the right format (though |
21 |
repoman doesn't check for it and yes developers can choose not to use |
22 |
these tools). I think changing them over to XML would be |
23 |
more overhead in file size and in required tools to parse them than is |
24 |
really necessary. If the problem is that people can't follow directions, |
25 |
then don't punish those of us who do. |
26 |
|
27 |
Additionally XML is not (despite what many developers may think) easily |
28 |
human readable to those who don't understand how markup languages |
29 |
generically work. And even to some of us that know how, it's still (for |
30 |
lack of a better phrase) a royal PITA. |
31 |
|
32 |
While if this was solely a community of developers or technically savvy |
33 |
people, then perhaps using XML-based ChangeLogs would be OK. However |
34 |
it isn't and I think that would be a poor assumption on our part. Yes |
35 |
you could make a tool to make it human readable, but again that's more |
36 |
overhead you do not need if you can get developers to correctly input |
37 |
their ChangeLog entries now. |
38 |
|
39 |
Considering the file "ChangeLog" in an of itself is almost an unofficial |
40 |
standard that assumes a plain text document, should such a decision be |
41 |
made to go with XML-based ChangeLogs, perhaps we should give them another |
42 |
name. |
43 |
|
44 |
|
45 |
But yeah, that's my $0.02/rant 'n' rave. |
46 |
- -- |
47 |
Jason Wever |
48 |
Gentoo/Sparc Co-Team Lead |
49 |
-----BEGIN PGP SIGNATURE----- |
50 |
Version: GnuPG v1.2.4 (GNU/Linux) |
51 |
|
52 |
iD4DBQFA/nLndKvgdVioq28RAstZAJi6VfQX34lTgrfDsoEbU+x2c6kOAKCX80DK |
53 |
jg9FctPiw7OSTQzLHCVMxQ== |
54 |
=7BAm |
55 |
-----END PGP SIGNATURE----- |
56 |
|
57 |
-- |
58 |
gentoo-dev@g.o mailing list |