Incorrect link provided in cue help cmd output

[cueckoo]

Originally opened by @garethr in cuelang/cue#39

The current output points folks to http://cuelang.org/pkg/tool for information on available tasks. However that URL doesn't have any content.

$ curl -i http://cuelang.org/pkg/tool
HTTP/1.1 404 Not Found
Content-Type: text/plain; charset=utf-8
X-Content-Type-Options: nosniff
X-Cloud-Trace-Context: 06cb78cc27dfe93e8cc9dd3bde03b522;o=1
Date: Mon, 22 Apr 2019 10:32:57 GMT
Server: Google Frontend
Content-Length: 19

404 page not found

[cueckoo]

Original reply by @mpvl in cuelang/cue#39 (comment)

The higher-level pkg for tool is not yet committed as it still needs some work. Sorry about that. Right now the raw interface is available only, and the documentation are the examples in the kubernetes tutorial. The infrastructure for supporting these packages is done, though, and the APIs are mostly written. It is mostly a matter of picking the right place in the directory structure: the pkg directory contains the core library, but the tools libraries will only be available to the scripting layer. So ideally there is a nice directory outside the pkg dir to house them.

[cueckoo]

Original reply by @garethr in cuelang/cue#39 (comment)

Ah, makes sense. I was trying out some of the examples in the inline help and ran into issues with the missing packages. I was in particular interested in outputting to files which I presume is in there? eg.

task write: file.Append({

[cueckoo]

Original reply by @mpvl in cuelang/cue#39 (comment)

The solution is simple, actually. It is fine (and possibly useful) to gives access the tool definitions within the normal package directory --- it is just data ---, as long as the corresponding functionality is not accessible from the non-tool cue files. So it can share the pkg directory without issue.

I'll work on getting this in asap.