This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
In message <19990305184852.5825.qmail@deer>you write: > Jeff and others, before we get too closed-down on the 1.1.2 front, > could y'all make sure we'll ship it with good pointers to live > information on the web pages regarding bugs and news? I don't think we should hold up a release for this, at least not this release. It'd be nice if we can get it in, but if we can't, then we should move on, much like any other new feature. If we can get it in, great. If not we put it on the egcs-1.2 list and let it compete for time with all the other things that need to be addressed. > In particular, Jeff, the cgi-bin/fortrannews and cgi-bin/fortranbugs > scripts (which I can't find in my checked-out copy of wwwdocs, FWIW) > seem *nearly* ready for prime-time, and I'd like them to replace > the fortran.html stuff I recently updated by hand-tweaking the > outputs of texi2html over bugs.texi and news.texi. The cgi scripts aren't particularly well suited for inclusion in a distribution since they rely on being able to grope around in the cvs repository. Nor are we currently shipping our entire web site content with releases. Maybe we should, but that's not a change I want to make this late in the game. Right now we ship the install directory and the FAQ. Before we start adding to that I'd like to have a little better picture for how it fits into the distributions. [ The cgi scripts aren't in the repo because I haven't checked them -- they were intended to show the kinds of things we can do. Checking them in is a trivial thing to do though. ] > So, I'm thinking there shouldn't be any equivalent to fortran.html > in the egcs-1.1.2 info on the web page -- though there should be a > link to the new bugs/news info that's automatically generated. This sounds reasonable and easy. Where precisely do you want me to link in the cgi scripts? And when you answer that question I suspect you'll find that you do want a Fortran page, which has links to the bug list and news items (and possibly the entire Fortran manual). > What I'm especially interested in seeing is the top-level egcs page > contain two items: > > We try to provide late-breaking information on *known bugs*, and > *news* about items already planned for upcoming releases. Again, I don't think we're really in a position to do this. And I'd prefer to have a little more of a clue how to tie this stuff in before we start adding it to distributions. Consider that the html pages we include in the distribution are meant to be viewed locally. Now you want to have some content remote. Keeping these links correct with a mixture of local and remote content isn't trivial. Let's get the info on our web page in some manner, but not try to suck it into the distributions yet. That gives us time to experiment and actually think through the distibution issues. > As far as fixing things so fortranbugs and fortrannews properly > honor @ifhtml and @ifnothtml -- right now, fortranbugs starts off > looking pretty silly, in the middle of a sentence, apparently > due to this -- let me know if I can help. I'm a bit of a toolsmith, > though I don't think I have the sources to things like texi2html > handy. (E.g. if you want me to write a quicky pre-filter for it, > or something, I could do that. Not sure which language would be > appropriate, though, and I don't know Perl yet.) Well, based on earlier conversations I think instead of farting around with @ifhtml and friends that longer term we should have the whole manual online in html form with links directly into the bugs and news section. In such a scheme you'd want @ifhtml/@ifnothtml only for things which you want to appear in the texi or html docs, but not the other. I doubt there's much content of this nature. jeff