Considering a recent comment about pdf files, I ask... What should be included in the dist file?
Obviously all source, including the manual. What about some things that are not source? Documentation: 1. HTML files? 2. DVI files? 3. PDF files? 4. PS files? My comment: People should be able to read the docs doing anything else. Requiring the tools to compile finished documentation adds another dependency. Should there be another file, distributed next to the source one, with finished docs? Should several options be offered: 1. complete (including processed docs) 2. source only 3. processed docs 4. testing files --- this is 4 files offered for download. One common mistake I see is to give only short names for the files, so I am not sure what I need. So, I download them all only to discover duplication. What about regression test files? (the test subdir). Does anyone actually use them? Does anyone else know how to interpret the results? Comment: With floating point, often you don't get an exact match. I have seen it different between Intel and AMD processors. I looked at the GNU standards to see if there is a way they recommend. I didn't see anything. I solicit opinions in this. I have no bias toward any particular way of doing it. _______________________________________________ Gnucap-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnucap-devel
