Here are some patches for html files containing reference to STLport project to fix the location to the really active project on sourceforge. index.html.path for boost/lib/compatibility/index.html platforms.html.patch for boost/libs/python/doc/v2/platforms.html tools.html.patch for boost/tools/build/v2/doc/tools.html I would like to update information about STLport project but I cannot find all boost web file or documentation in CVS. Sorry if I miss something, I cannot follow boost evolution every days, but where has all the doc gone ? Bests --- index.html.orig 2007-02-23 19:00:21.908448000 +0100 +++ index.html 2007-02-23 19:01:17.738728000 +0100 @@ -49,7 +49,7 @@ </ul> <p>There are more powerful alternatives to using the Boost.Compatibility - library CXX headers, e.g. <a href="http://www.stlport.org/">STLport</a> + library CXX headers, e.g. <a href="https://sourceforge.net/projects/stlport">STLport</a> or <a href= "http://www.fnal.gov/docs/working-groups/fpcltf/Pkg/ISOcxx/doc/0ISOcxx.html"> ISOCXX</a>. However, in contrast to these alternatives, the --- platforms.html.orig 2007-02-23 19:07:20.920958400 +0100 +++ platforms.html 2007-02-23 19:08:03.602331200 +0100 @@ -93,7 +93,7 @@ <dt><a href= "http://msdn.microsoft.com/visualc/default.asp">Microsoft Visual - C++ 6</a> with <a href="http://www.stlport.org">STLPort + C++ 6</a> with <a href="https://sourceforge.net/projects/stlport">STLPort 4.5.3</a></dt> <dt><a href= @@ -106,7 +106,7 @@ <dt><a href= "http://www.intel.com/software/products/compilers/c60/">Intel C++ - 5.0</a> with <a href="http://www.stlport.org">STLPort + 5.0</a> with <a href="https://sourceforge.net/projects/stlport">STLPort 4.5.3</a></dt> <dt><a href="http://www.cygwin.com">Cygwin</a> <a href= --- tools.html.orig 2007-02-23 19:09:24.338424000 +0100 +++ tools.html 2007-02-23 19:09:43.445899200 +0100 @@ -49,7 +49,7 @@ <p>Some important libraries have special support in Boost.Build:</p> <ul> - <li><a href="http://stlport.org">STLport</a> — on gcc and + <li><a href="https://sourceforge.net/projects/stlport">STLport</a> — on gcc and msvc.</li> <li><a href="http://www.trolltech.com/products/qt/index.html">QT</a>,
On Fri, 23 Feb 2007 20:40:04 -0000, François Dumont <francois.cppdevs@free.fr> wrote:
Here are some patches for html files containing reference to STLport project to fix the location to the really active project on sourceforge.
index.html.path for boost/lib/compatibility/index.html platforms.html.patch for boost/libs/python/doc/v2/platforms.html tools.html.patch for boost/tools/build/v2/doc/tools.html
I would like to update information about STLport project but I cannot find all boost web file or documentation in CVS. Sorry if I miss something, I cannot follow boost evolution every days, but where has all the doc gone ?
I guess you're thinking of the links to stlport from the Boost Build v1 documentation, such as: http://www.boost.org/tools/build/v1/stlport.html But Boost Build v1 has been removed so it's no longer in CVS. I'm not sure what's happening to it when 1.34 is released. There's also a link in 'libs/config/config.htm'. And some links to stlport in '/more/generic_exception_safety.html' but they point to documents that don't seem to be on the sourceforge site and refer to work on early versions of STLport, so they should probably be left alone. The links in the Boost.Python documentation are referring to STLPort 4.5.3 - so it might be best to leave them alone. In the patch you changed the links to the sourceforge project page (https://sourceforge.net/projects/stlport), I think the new home page would be a friendlier (http://stlport.sourceforge.net). Hopefully that's okay with you? I changed the subject to try to get the attention of the relevant library maintainers, any objections to changing the links? If I don't hear any, I'll go ahead and do it. I've attached an updated patch for build, compatibility and config. Also, would it be okay to add these changes to 1.34? Daniel
Daniel James wrote:
On Fri, 23 Feb 2007 20:40:04 -0000, François Dumont <francois.cppdevs@free.fr> wrote:
I changed the subject to try to get the attention of the relevant library maintainers, any objections to changing the links? If I don't hear any, I'll go ahead and do it. I've attached an updated patch for build, compatibility and config.
Also, would it be okay to add these changes to 1.34?
Please do! Thomas -- Thomas Witt witt@acm.org
participants (3)
-
Daniel James -
François Dumont -
Thomas Witt