143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
|
1. **Vendor the client** as above.
2. **Add pkgt to the Eagle package path**, then run setup:
```tcl
# Inside Eagle
set pkgtRoot [file normalize "./vendor/pkgt"]
path add [file join $pkgtRoot client 1.0 neutral]
# Optional: also add externals if not on your path already
path add [file join $pkgtRoot externals Eagle lib Eagle1.0]
# Run interactive/CLI setup to register repository endpoints and API keys:
source [file join $pkgtRoot client 1.0 neutral pkgr_setup.eagle]
```
3. **Pre‑install (optional)**:
|
|
|
|
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
|
1. **Vendor the client** as above.
2. **Add pkgt to the Eagle package path**, then run setup:
```tcl
# Inside Eagle
set pkgtRoot [file normalize "./vendor/pkgt"]
lappend ::auto_path [file join $pkgtRoot client 1.0 neutral]
# Optional: also add externals if not on your path already
lappend ::auto_path [file join $pkgtRoot externals Eagle lib Eagle1.0]
# Run interactive/CLI setup to register repository endpoints and API keys:
source [file join $pkgtRoot client 1.0 neutral pkgr_setup.eagle]
```
3. **Pre‑install (optional)**:
|
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
|
### Uploading / publishing
Use the **uploads** client and/or helper:
```tcl
# Eagle
set pkgtRoot [file normalize "./vendor/pkgt"]
path add [file join $pkgtRoot client 1.0 neutral]
# Upload tool:
source [file join $pkgtRoot client 1.0 neutral pkgr_upload.eagle]
```
> The repository (metadata) server is managed via a web UI; the file server typically runs on **Fossil** and uses repository users/keys for access. Public and private publishing models are supported.
|
|
|
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
|
### Uploading / publishing
Use the **uploads** client and/or helper:
```tcl
# Eagle
set pkgtRoot [file normalize "./vendor/pkgt"]
lappend ::auto_path [file join $pkgtRoot client 1.0 neutral]
# Upload tool:
source [file join $pkgtRoot client 1.0 neutral pkgr_upload.eagle]
```
> The repository (metadata) server is managed via a web UI; the file server typically runs on **Fossil** and uses repository users/keys for access. Public and private publishing models are supported.
|