Ports module stabilization todo

[Yohe-Am]

• Ports 0.2 redesign #44

• Formalize runtime dependencies

• Dynamic port dependencies

  • When using ports like npmi and specially, cargobi, ports might rely on other different build and runtime ports depending on their configuration. For e.g. cargobi will need the rust toolchain if cargo-binstall is unable to find a binary distribution of the crate. The rust-toolchain here is a dynamic dependency is as it's only needed in certain cases. Without explicit support for them, the toolchain is always downloaded first even if it doesn't end up being used.
  • Optional port dependencies

• Installation sets feat!: envs module #46

• Ports sandboxing #9

• Version fuzzy matching Version fuzzy match #16

• Lockfiles

  • Lockfile that includes serialized config stored next to ghjk.ts and put in version control feat: tasks and lockfiles #28
  • For deno based workers, shasum of their modules
    • This is being tracked in hash.json
  • Track dynamic imports in hash.json #74
  • Clean and compact lockfile format

• Keep track of if an InstConf has completed it's download, install step. (consider Deno.kv) feat: tasks and lockfiles #28

  • Move to a .meta file based approach to make ports dir portable. .meta file based port db #68

• Formalized approach for prompting users for input

  • Values are recorded in the lockfile to avoid issues in CI?

• Windows support #76

• Use shimscripts to harden the default dep ports. You can probably do a lot of damage to someone's system using just bsdtar

  • Remove cpy_bs and node from the default dep ports list feat(tests): improve test suite #27
  • Non ambient support for std deps
    • Lower git from ambient to concrete port. #78
    • Lower curl from ambient to concrete port. #77
    • tar Consider tightening tar ambient port to bsdtar  #23

• Move most ports to separate repository

  • Nightly test runs for all ports for latest and set of specific pinned versions

• Test suite support for external port implementers

  • Think deno test https://ghjk/tests/e2ePortStandalone.ts myPort.ts '{ "version": "123"}'

• Xdg port installer script #75

• ghjk.yaml #73

• Use hash of manifest to identify ports

  • denoWorker will have the hash of their module file added to the manifest

• Support for ghjkfile provided hooks on port lifecycle. Basically, run ghjkfile tasks when ports are built/installed. Can be escape hatch of doing extra/freeform modifications on a system for edge cases.