So then I said to John: > > OK. Honestly, I don't think this would be hard to do, I just haven't had > time to figure it myself. At first blush, it would seem that the links > would be generated from the overarching definition of EMC2 document > organization, which for us is contained in the Submakefile, not the > individual txt files, because that's where you learn about which follows > what. As an aside, this use of the Submakefile is perfectly legitimate > but goes against my personal sense of coding practice. Left to my own > devices, I'd put the stuff related to the organization of EMC2 > documentation into a separate file. Then I could quickly change the > organization without touching any of the low-level apparatus like > Makefile/Submakefile. But that's just me.
Well, duh. I don't know what I was smoking. Obviously in v2.5 the Master_xxx.txt files have everything to do with the document organization. Sorry. I shouldn't write email when I'm harried. Regards, Kent ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
