Erik,
Sorry ... "one of our products" wasn't referring to an Apache product, which
is why I went on to look for some Open Source products to do the job. :-)
> I only used linklint so far; it's easy to setup and provides detailed
reports.
I just loaded it up onto one of my internal systems
linklint -http -host <project>.apache.org -limit 5000 -doc
sites/<project>.apache.org /@
Is that the best set of options, or is that a bit too naive? From the site
report, it looks as if the best thing would be to put the results somewhere
on daedalus or icarus, and post e-mail saying that the results are
available.
Would you be willing/able to help set it up? Would it be best to run it on
one of the apache servers, or a third-party machine? I suspect that the
configuration ought to be kept in a CVS module available to Committers,
which could be updated to the linklint server before each run. Once setup,
a cron job could kick it off at the desired schedule.
--- Noel
-----Original Message-----
From: Erik Abele [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 02, 2003 15:35
To: community@apache.org
Subject: Re: Verifying links
Noel J. Bergman wrote:
> Erik,
>
> You are most welcome. And thank you for searching that list. :-)
>
> Although each PMC is ultimately responsible for their content, it does
seem
> to me that it is a lot of redundant effort (and likely not commonly done)
to
> scan for broken links.
You're absuletely right, it would minimize a lot of redundant work and
ensure that it is really done.
However, since I rarely came across broken links on the ASF pages I just saw
no need for it up to now, but I would be very fine with such a system :)
> We have a link checker built into one of our products, but I'm sure that
> there are other open source tools for that purpose that could be batched,
> e.g.,
>
> http://www.linklint.org/
> http://validator.w3.org/docs/checklink.html
I only used linklint so far; it's easy to setup and provides detailed
reports. Wich 'of our products' do you mean? Sorry, don't know every project
of the Jakarta world :-(
>
> Something like one of those could be batched from time to time, and the
> report mailed to the appropriate list.
As said above, would be handy to have such a tool; just go for it ;-)
cheers,
Erik
>
> --- Noel
>
> -----Original Message-----
> From: Erik Abele [mailto:[EMAIL PROTECTED]
> Sent: Sunday, February 02, 2003 12:28
> To: community@apache.org
> Subject: Re: Verifying links
>
>
> Thanks for the reminder to Eric Raymond's changes :)
>
> Just grep'ed httpd-*, site, site-tools, apr-*, incubator-*, asf-site,
> commons-* and found only 3 incorrect links.
>
>
>>In any event, I'm wondering about the systematic issue.
>
>
> Do you think about a general link-checker installed on daedalus? Hmmm, is
> this really needed? IMHO this should be the responsibility of the
> content-producing group.
>
> cheers,
> Erik
>
> Noel J. Bergman wrote:
>
>>Are the *.apache.org sites ever scanned for broken links?
>>
>>I noticed to day that Eric Raymond moved his personal web site from
>>tuxedo.org to catb.org, invalidating all links to tuxedo.org. See
>>http://hurkle.thyrsus.com/~esr, which says "My site has moved to
>>http://www.catb.org/~esr/. Please fix your bookmarks accordingly. Just
>>change `tuxedo' to 'catb' in each URL."
>>
>>There are links to his old URL, e.g., from
>>http://jakarta.apache.org/site/library.html.
>>
>>In any event, I'm wondering about the systematic issue.
>>
>> --- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
