DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22714>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22714 It would be nice if ./configure would automatically sed the documentation ------- Additional Comments From [EMAIL PROTECTED] 2003-08-31 09:17 ------- Suggestion on "better documenting how the paths are selected and discovered." Creating a customized RPM or MSI distribution either, forces the maintainer to make his/her mind up with a deep conceptual understanding of the "paths". From a package maintainers point of view i'd like to call this "logical paths". Providing a kind of "map" in the manual tree explaining the transition from "logical paths" ("./configure"'s point of view) to the resulting paths in a concrete installation (the user's point of view) might help. That "kind of a map" could be implemented as table or an image, an would be bound somewhere in the "installation" section of the manual. This avoids to "sed" the manual as whole - only the "map" would be generated/manipulated during build and/or install. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
