Wireshark · Wireshark-dev: Re: [Wireshark-dev] So why does building stuff in the docbook directory use DocBook URLs *and* disab

Wireshark-dev: Re: [Wireshark-dev] So why does building stuff in the docbook directory use DocB

From: Guy Harris <guy@xxxxxxxxxxxx>

Date: Sat, 29 Apr 2017 02:16:17 -0700

On Apr 29, 2017, at 1:56 AM, Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:

> This fails when there’s no catalog to map the URL to a local resource.

What is a "local resource" in this context?  Why is there a need to map it to a local resource, rather than just reading it from the URL in question?

Removing --nonet seems to make it Just Work on my Mac with the version of AsciiDoc I downloaded, built, and installed ages ago.

Follow-Ups:
- Re: [Wireshark-dev] So why does building stuff in the docbook directory use DocBook URLs *and* disable fetching stuff over the net?
  - From: Jaap Keuter

References:
- [Wireshark-dev] So why does building stuff in the docbook directory use DocBook URLs *and* disable fetching stuff over the net?
  - From: Guy Harris
- Re: [Wireshark-dev] So why does building stuff in the docbook directory use DocBook URLs *and* disable fetching stuff over the net?
  - From: Jaap Keuter

Prev by Date: Re: [Wireshark-dev] So why does building stuff in the docbook directory use DocBook URLs *and* disable fetching stuff over the net?
Next by Date: Re: [Wireshark-dev] Devices in tshark versus dumpcap
Previous by thread: Re: [Wireshark-dev] So why does building stuff in the docbook directory use DocBook URLs *and* disable fetching stuff over the net?
Next by thread: Re: [Wireshark-dev] So why does building stuff in the docbook directory use DocBook URLs *and* disable fetching stuff over the net?
Index(es):
- Date
- Thread