boost 1.42.0_0 installation structure non-boost standard

[mostafa_working_away@…]

Open ​file:///opt/local/share/doc/boost/libs/serialization/doc/archive_reference.html.

The links in the following paragraph from the webpage are broken:

Start As a convenience, small header files have been included which contain typedef for polymorphic implementation for each corresponding templated one. For example, the headers polymorphic_text_iarchive.hpp and polymorphic_text_oarchive.hpp. contain the typedef for the polymorphic implementation of the standard text archive classes text_iarchive.hpp and text_oarchive.hpp respectively. All included polymorphic archives use the same naming scheme. End

For example polymorphic_text_iarchive.hpp points to ​file:///opt/local/share/doc/boost/boost/archive/polymorphic_text_iarchive.hpp which is a non-existent location. Talking with the boost crowd they said it was a packaging issue. Note that it uses a relative path in the link. Note that it should point to /opt/localinclude/boost/archive/polymorphic_text_iarchive.hpp

Which suggests that the boost documentation should be installed in a subdirectory of /opt/local/include/boost

[mostafa_working_away@…]

Also, open ​file:///opt/local/share/doc/boost/libs/serialization/doc/index.html, and compare the left frame menus to ​http://www.boost.org/doc/libs/1_42_0/libs/serialization/doc/index.html, note how the java-script tree structure is broken in the macports version. NOTE: this works in the boost source that I've downloaded and tested locally, so it's not a special feature that requires web hosting.

[nox@…]

That may be their standard installation layout, but I won't install headers alongside the doc neither I will install the doc alongside the headers. That's not standard. At all.

I will try to change to paths in the doc.

[mostafa_working_away@…]

The first problem is easily solved by creating a symbolic link in /opt/local/share/doc/boost/ named "boost" which points to /opt/local/include/boost/. This should be a lot easier than changing all the paths in the docs.

The second problem is of a different type. For some reason the *.gifs in {boost source code head}/libs/serialization/doc/ were not copied over to /opt/local/share/doc/boost/libs/serialization/doc/. Once this is done, then one gets the javascript tree expandable structure in the left frame.

[mostafa_working_away@…]

Note, concerning the second proposed solution, I wonder if failing to copy the *.gif files is a symptom of a much larger bug.

[mostafa_working_away@…]

Another missing file, the direcotry ​file:///opt/local/share/doc/boost/libs/iostreams/doc/tree is missing tree.js, which is in the boost tar. Without it, the menu in the left pane of ​file:///opt/local/share/doc/boost/libs/iostreams/doc/index.html would be missing.

[nox@…]

Maintainership relinquished in r69969.

[mostafa_working_away@…]

All issues fixed as of Revision 70711.