Title: Spike: can the new Spago consume the Lua package set directly? · Issue #115 · purescript-lua/purescript-lua · GitHub
Open Graph Title: Spike: can the new Spago consume the Lua package set directly? · Issue #115 · purescript-lua/purescript-lua
X Title: Spike: can the new Spago consume the Lua package set directly? · Issue #115 · purescript-lua/purescript-lua
Description: Tracked here for one place; the actual deliverable lands in purescript-lua/purescript-lua-package-sets (and possibly the fork repos). Context: #55 migrated the pslua test project to the new Spago (spago.yaml + registry). The new Spago dr...
Open Graph Description: Tracked here for one place; the actual deliverable lands in purescript-lua/purescript-lua-package-sets (and possibly the fork repos). Context: #55 migrated the pslua test project to the new Spago (...
X Description: Tracked here for one place; the actual deliverable lands in purescript-lua/purescript-lua-package-sets (and possibly the fork repos). Context: #55 migrated the pslua test project to the new Spago (...
Opengraph URL: https://github.com/purescript-lua/purescript-lua/issues/115
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Spike: can the new Spago consume the Lua package set directly?","articleBody":"Tracked here for one place; the actual deliverable lands in `purescript-lua/purescript-lua-package-sets` (and possibly the fork repos).\n\nContext: #55 migrated the pslua test project to the new Spago (`spago.yaml` + registry). The new Spago dropped Dhall, and the Lua package set publishes only a Dhall `packages.dhall`, so it can no longer be pointed at as a package set. The consumer (`test/ps/spago.yaml`) now hard-codes every FFI fork as an `extraPackages` git override with an **inlined dependency list**, duplicating the set's data and drifting from it.\n\nQuestion to resolve: can the new Spago (>= 1.x) consume a set published by `purescript-lua-package-sets`, so consumers point at one URL instead of enumerating git overrides?\n\nInvestigate:\n\n- Does `workspace.packageSet.url` (or a local path) accept a *custom, non-registry* set, and does its schema allow `git` + `ref` package entries (the way the Dhall set's `repo` + `version` do)? Or is the URL format restricted to registry `name -> version` maps?\n- If git entries are not supported in a custom set: would the forks have to be published to the PureScript Registry to appear in a registry-format set? Are these `.lua`-FFI forks registry-eligible at all?\n- Produce a minimal PoC: a candidate set file plus a `spago.yaml` that consumes it and builds a trivial module against a couple of forks.\n\nOutcome: a decision note — (A) publish a consumable set (define the format + release mechanics) or (B) fall back to per-fork `spago.yaml`. This spike gates the strategy-(b) issue.","author":{"url":"https://github.com/Unisay","@type":"Person","name":"Unisay"},"datePublished":"2026-06-23T15:14:11Z","url":"https://github.com/purescript-lua/purescript-lua/issues/115"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:a742b6e3-12d3-b9a2-775b-9f25206add71 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B420:2978F1:A109B7:D161BB:6B00E458 |
| html-safe-nonce | 132776fb549420e6e9b7031eae648367d8e22d6a1957e86545c21305113f437a |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCNDIwOjI5NzhGMTpBMTA5Qjc6RDE2MUJCOjZCMDBFNDU4IiwidmlzaXRvcl9pZCI6IjMwNDM4ODA3NDk3OTI1NTM4NCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 65e01d0400f4e0d6bede8d3fa5650229e1bb0f0f17b1b198041d8194fc4f0c04 |
| hovercard-subject-tag | issue:4727113346 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/purescript-lua/purescript-lua/115/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d8d8b833dd1cdc7aaf9e1934b0c7ae375baf5e3db4143cbf5ab5e0982829c4e9/purescript-lua/purescript-lua/issues/115 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d8d8b833dd1cdc7aaf9e1934b0c7ae375baf5e3db4143cbf5ab5e0982829c4e9/purescript-lua/purescript-lua/issues/115 |
| og:image:alt | Tracked here for one place; the actual deliverable lands in purescript-lua/purescript-lua-package-sets (and possibly the fork repos). Context: #55 migrated the pslua test project to the new Spago (... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | Unisay |
| hostname | github.com |
| expected-hostname | github.com |
| None | 27088b6977484d0d3321d9a11c907c6d6637b315cfa359ef7952dbf6292f9b14 |
| turbo-cache-control | no-preview |
| go-import | github.com/purescript-lua/purescript-lua git https://github.com/purescript-lua/purescript-lua.git |
| octolytics-dimension-user_id | 131581790 |
| octolytics-dimension-user_login | purescript-lua |
| octolytics-dimension-repository_id | 587200487 |
| octolytics-dimension-repository_nwo | purescript-lua/purescript-lua |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 587200487 |
| octolytics-dimension-repository_network_root_nwo | purescript-lua/purescript-lua |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 624179fb8b88d26ba5bba08894eb60a1c5a1d93d |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width