58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
+
+
-
+
-
+
|
│ ├─ Eagle/lib/Eagle1.0/ # Eagle library packaged for Tcl
│ └─ Harpy/Tools/sign.eagle# Harpy code-sign tooling
├─ tools/
│ ├─ deploy.bat
│ ├─ pkgr_an_d_get.sh
│ └─ pkgr_an_d_install.sh # helper scripts to fetch/install the client
└─ doc/
├─ redirector_v1.html # URN/URL redirector server documentation (reference)
├─ repository_v1.html # package metadata server documentation (reference)
└─ v1.html # v1 toolset documentation (reference)
└─ toolset_v1.html # package client toolset documentation (reference)
```
> File names and layout above come from the initial import. See the commit tree for the authoritative list. The current version is **1.0.11**.
> File names and layout above come from the initial import(s). See the commit tree for the authoritative list. The current version is **1.0.11**.
---
## Security model at a glance
* **Metadata path**: The client asks a repository service for a package that satisfies a **TIP #268** version requirement. The server returns a small **signed script** that knows what to fetch.
* **File path**: The client downloads one or more **OpenPGP‑signed** files and verifies them **before** the package is made available to the interpreter.
|
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
|
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
|
-
+
|
* **Run once**: `pkgr_setup.eagle` to register:
* One or more **repository endpoints** (metadata server URLs).
* **File server** base URLs.
* API keys (**read** and **full**) for private/personal repositories.
* **Persisted settings**: setup writes settings that subsequent runs of the client will use automatically (both for on‑demand resolution and pre‑installation). See `doc/v1.html` for parameter names and advanced options.
* **Persisted settings**: setup writes settings that subsequent runs of the client will use automatically (both for on‑demand resolution and pre‑installation). See `doc/toolset_v1.html` for parameter names and advanced options.
---
## FAQ
**Q. Does this replace `pkgIndex.tcl`?**
A. No. pkgt **uses** normal package metadata; it just enables secure **remote** resolution and delivery when a required package is not available locally.
|