I agree that it's frustrating. It simply hasn't kept up with the
scale of growth that we've seen.
I have previously attempted to be break it up into multiple pieces.
There are several issues with that that will require a lot of rewrite
in the infrastructure to handle. They are not difficult issues, but
it has been lower priority than getting Fuerte into shape.
If someone has a hankering to take a stab at rewriting the indexer, I
am happy to pass the baton.
There is also a 'backdoor' that I can give you access to that is
useful for "one-time" spins that gives quick turn for a single
repository. It violates many of the issues that I allude to above,
which is why it is only for emergency use. If this is the case for
you, I can show you how to use that.
If it is the case that you're simply pointing to documentation for a
doc/api review, one solution is to just build the doc set locally and
upload it to the web. The advantage to this approach is that you are
pointing to a versioned set of documentation.
- Ken
On Sun, Feb 19, 2012 at 11:43 AM, Jack O'Quin <
jack.oquin@gmail.com> wrote:
> The ROS documentation indexer has not completed a pass for many days
> now. That can be frustrating when trying to finish development for a
> new release.
>
> I recall hearing that it often gets stuck polling various unresponsive sites.
>
> Is there some way the list could be broken into multiple pieces, with
> reliable sites visited nightly and others on a "best can do" schedule?
> --
> joq
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
(text/plain)