[M3devel] some testing of the new web pages

[Jay]

I do like the new web pages.
Here are some problems though.
 

http://www.opencm3.net/releng/collection-core.html
 

go down to m3-sys/cm3
the builder and freebsd manual page links aren't right.
I think these are maybe just CVS merge conflicts
that happen to be on the packaging machine and
can just be deleted.

Not clear if most of the gcc links are useful.
 

go down to TCL interfaces for M3
The browse sources link doesn't work.
Probably related to this not always building and not built.
Probably need to modify this and require people doing package building
to have Tcl installed, maybe even for NT386.
Probably specifically make-dist.sh should set $ENABLE_TCL or somesuch.
  (not exactly) 
 
 
The source links present, e.g. the licenses oddly,
but compactly and probably a good thing, e.g.:
http://www.opencm3.net/doc/help/gen_html/tcp/src/common/StreamRdClass.m3.html
Probably an artifact of m3tohtml.
 

http://www.opencm3.net/releng
Go down the righthand side trying everything to one level.
Broken:
 http://www.opencm3.net/releng/collection-min.html
 http://www.opencm3.net/releng/collection-caltech.html
 

But there is:
 http://www.opencm3.net/releng/collection-caltech-parser.html 
   It contains m3-win/import-libs but shouldn't.
 

I suspect the problems are rooted in:
  min is a non-ws package set but not a ws package set.
  Because it is overlys small and core subsumes it?
  caltech-parser contains a dash.
  min to me is specifically enough to start with an old release and 
   build a current compiler and release -- m3core, libm3, m3cg, cm3, maybe sysutils 
   specifically it is the pieces required to compile anything (cm3, m3cg) 
   and the pieces that an old compiler may not be able to build the 
   the current versions of (m3core/libm3) that a current compiler will need;
   That is, if you want to build natively build the whole system from source,
   this is the smallest you can start with. m3cg actually isn't in min but
   probably handled specially.
 

Related couments usually but not always
has one extra empty bullet, including but not limited
to when the list is empty:

 http://www.opencm3.net/releng/collection-cvsup.html
 http://www.opencm3.net/releng/collection-anim.html
 http://www.opencm3.net/releng/collection-cvsup.html
 http://www.opencm3.net/releng/collection-database.html
 http://www.opencm3.net/releng/collection-demo.html 
 http://www.opencm3.net/releng/collection-devlib.html 
 http://www.opencm3.net/releng/collection-game.html 
 http://www.opencm3.net/releng/collection-gui.html 

This is not all the ones with an extra bullet, and a few
don't have the extra bullet.

I'm on the fence on the whole ws thing.
Non-ws also has matching source.
The point is to provide the packages both built
and buildable?
If cm3 had a mode that started with assemble then link and ship,
we could cross build all the ws packages, very nice.

I guess the "real" problem is I feel compelled then to
match this feature in make-dist.py.

http://www.opencm3.net/releng/collection-tool.html
 Try the first few links.
  mtex
   Browse sources seems incomplete but maybe is right.
   The man page links are all broken.
 
   cmpdir
     shows a general pattern:
     maybe directories with no files shouldn't be shown?

http://www.opencm3.net/releng/collection-demo.html
  fisheye
    The link manual page .makefile isn't right
 

 http://www.opencm3.net/releng/collection-devlib.html
  m3tk
    Several broken manpage links.

  pex
   browse sources doesn't work
   Probably like Tcl, not always built.
 

http://www.opencm3.net/releng/collection-anim.html
   zeus
   contains a broken Zeus manual page, I think a CVS conflict file
  Might be able to search for this generally in the html.

http://www.opencm3.net/releng/collection-obliq.html
  related documents
   first link, to polymtl, broken, sounds promising, maybe
    we can find it and host it

 http://www.opencm3.net/releng/collection-m3gdb.html
  m3gdb
   Like m3cc, maybe some of these READMEs not useful.
 

 - Jay