Title: Factor the CLI executable into its own package · Issue #136 · github/semantic · GitHub
Open Graph Title: Factor the CLI executable into its own package · Issue #136 · github/semantic
X Title: Factor the CLI executable into its own package · Issue #136 · github/semantic
Description: Today the builders decided to recompile the universe from scratch because a cabal new-update gave us some new bugfixes. While the build time is unfortunate (see #88), I started thinking about a separate dilemma, to wit: as time goes on a...
Open Graph Description: Today the builders decided to recompile the universe from scratch because a cabal new-update gave us some new bugfixes. While the build time is unfortunate (see #88), I started thinking about a sep...
X Description: Today the builders decided to recompile the universe from scratch because a cabal new-update gave us some new bugfixes. While the build time is unfortunate (see #88), I started thinking about a sep...
Opengraph URL: https://github.com/github/semantic/issues/136
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Factor the CLI executable into its own package","articleBody":"Today the builders decided to recompile the universe from scratch because a `cabal new-update` gave us some new bugfixes. While the build time is unfortunate (see #88), I started thinking about a separate dilemma, to wit: as time goes on and we loosen/tighten library version bounds in response to new packages coming in over the wire, we risk introducing changes into the behavior of the `semantic` executable. Ideally we want the `semantic` library’s version bounds to be flexible, so as not to lock external consumers into a fixed library version. In contrast, we want executable builds to be reproducible, which means that a given release of the `semantic` command line tool should be built with a vetted, deterministic set of dependencies. Distributing both the library and the command line tool together in the same package—that is, trying to have flexibility and determinism simultaneously, in the same package—may render this difficult.\r\n\r\nI think what would be more correct would be to have `semantic` and `semantic-cli` packages, and use `cabal new-freeze` to provide `semantic-cli` with a `cabal.project.freeze` file that specifies the specific versions to use if someone wants to `cabal install semantic-cli` (and get the same executable that we’ve vetted and tested, not one built against libraries that we don’t know from Adam). Sort of like how `Cabal` the library and `cabal-install` the tool are separate things. I think? The documentation on `cabal new-freeze` implies that this is the right thing to do:\r\n\r\n> For end-user executables, it is recommended that you distribute the cabal.project.freeze file in your source repository so that all users see a consistent set of dependencies. For libraries, this is not recommended: users often need to build against different versions of libraries than what you developed against.\r\n\r\nIt’s not clear to me how a separate `semantic-cli` project in the same repository (and I would very much hope to use the same repository rather than a whole new one) would work. Hopefully the `cabal.project.freeze` files that `cabal new-freeze` files take effect lexically viz. not applying to the `semantic` library. \r\n\r\nGiven the relatively small user base of `semantic` the CLI tool, I don’t think this a crisis, nor do I necessarily insist on absolute and infallible build reproducibility: at this stage, the chances of production breakage creeping in due to version-bounds churn is very low, especially given our PVP contracts. I do, however, want to have an answer to this before we finish #16. ","author":{"url":"https://github.com/patrickt","@type":"Person","name":"patrickt"},"datePublished":"2019-06-13T03:34:37Z","url":"https://github.com/github/semantic/issues/136"}
| 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:723bf4c1-86bf-7db1-16a3-835a08139a85 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A746:10531B:1800A8B:1EA95A6:6B018470 |
| html-safe-nonce | c47bfafbc253e21f074348a7a5e55bef91c048b2d2baf71af485c69b2438933d |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBNzQ2OjEwNTMxQjoxODAwQThCOjFFQTk1QTY6NkIwMTg0NzAiLCJ2aXNpdG9yX2lkIjoiNDM5NzM1ODI5NTkyOTY4NTEwNSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 24df1acd593f8a07e11a8acf7aaad047e668df221d044b588565960526c344b8 |
| hovercard-subject-tag | issue:455519213 |
| 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/github/semantic/136/issue_layout |
| twitter:image | https://opengraph.githubassets.com/82d6eb10c0d48388d696f5d24b78492758a3bcde1fc19d0e3a6a7374791f35d5/github/semantic/issues/136 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/82d6eb10c0d48388d696f5d24b78492758a3bcde1fc19d0e3a6a7374791f35d5/github/semantic/issues/136 |
| og:image:alt | Today the builders decided to recompile the universe from scratch because a cabal new-update gave us some new bugfixes. While the build time is unfortunate (see #88), I started thinking about a sep... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | patrickt |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/github/semantic git https://github.com/github/semantic.git |
| octolytics-dimension-user_id | 9919 |
| octolytics-dimension-user_login | github |
| octolytics-dimension-repository_id | 175839913 |
| octolytics-dimension-repository_nwo | github/semantic |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 175839913 |
| octolytics-dimension-repository_network_root_nwo | github/semantic |
| 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 | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width