[Clfs-dev] Simplification of the XML
Joe Ciccone
jciccone at gmail.com
Sun May 30 17:21:55 PDT 2010
On 05/30/2010 08:03 PM, Ken Moffat wrote:
> On 29 May 2010 19:28, Joe Ciccone<jciccone at gmail.com> wrote:
>
>
>> My proposed change is simply an expansion on our current structure. Very
>> little in the actual layout will change, mostly files will just be merged
>> together rather then having way too many redundant xi:includes. Currently,
>> for each forked file we have one for every tag for every architecture. It's
>> ridiculous.
>>
>> I will implement this in a few sections of the book and see how it works
>> out.
> When I was editing here, there were always two problems - people making
> a change without testing if it allowed the book to generate, and changes
> which accidentally broke other architectures. Of the latter, I think I broke
> alpha at least twice. So, if the change makes the book less fragile, it will
> be worthwhile.
Yea, Alpha is one of those architectures that always seems to break. I'm
hoping that the book will become less fragile, as well as easier to
maintain.
> The possible downside is that it makes the resulting files hard to read and
> navigate (similar to the #idfdef problems that have sometimes occurred
> in C code). I have confidence in your judgement.
I know what you mean, But what is more complicated, 11 (at least, for
some packages like gcc 30+) separate files that all reference each other
or a single file with a few case like statements in it.
I'm almost done with a first pass converting up to cross-tools. There's
still a bit to do, but once I get it to a point where there's a few
usage examples, I will either push up my branch or tar it up and email
it to the list.
I guess its really down to a matter of the lesser of the two evils. As
soon as I finish with cross-tools I'll put up what I've got so far
before I hit the mother load (final system).
> ĸen
More information about the Clfs-dev
mailing list