184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
|
### Authoring a package
1. **Write your package** the normal Tcl/Eagle way:
* Provide a `pkgIndex.tcl` and/or `pkgIndex.eagle` that does `package provide <name> <version>`.
* Organize your files under a single directory named after your package.
2. **Test locally**: ensure `package require <name> <version>` works from a clean interpreter when your package directory is on `auto_path` (Tcl) or `path` (Eagle).
3. **Decide distribution mode**:
* **On‑demand**: pkgt can fetch files individually as directed by repository metadata.
* **Pre‑installable**: you can ship the package directory as a ready‑to‑use tree.
> The pkgt repository server resolves a TIP #268 version constraint, returns a small signed script, and instructs the downloader which files to fetch. All files are OpenPGP‑signed; Eagle files are also Harpy‑signed.
|
|
|
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
|
### Authoring a package
1. **Write your package** the normal Tcl/Eagle way:
* Provide a `pkgIndex.tcl` and/or `pkgIndex.eagle` that does `package provide <name> <version>`.
* Organize your files under a single directory named after your package.
2. **Test locally**: ensure `package require <name> <version>` works from a clean interpreter when your package directory is on `auto_path`.
3. **Decide distribution mode**:
* **On‑demand**: pkgt can fetch files individually as directed by repository metadata.
* **Pre‑installable**: you can ship the package directory as a ready‑to‑use tree.
> The pkgt repository server resolves a TIP #268 version constraint, returns a small signed script, and instructs the downloader which files to fetch. All files are OpenPGP‑signed; Eagle files are also Harpy‑signed.
|