Skip to content

Instantly share code, notes, and snippets.

@bbarker

bbarker/OI_packaging_discussion.md

Last active November 12, 2023 18:31
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save bbarker/118df6c47340c0a390c761624ccda447 to your computer and use it in GitHub Desktop.
Save bbarker/118df6c47340c0a390c761624ccda447 to your computer and use it in GitHub Desktop.
Download ZIP
OI packaging discussion 11/12/2023
Raw
OI_packaging_discussion.md
  • https://repology.org/
    • doesn’t notify maintainers
    • provides a view of which packages are out of date
      • Till has a prototype that will bump versions “the forge” / activity pub
  • Docs - priority is to guide new people into the process of contributing in various ways process
  • OminoOS uses a patched version of illumos, including patches for linux branded zones
    • These apparently did not meet the requirements of getting upstreamed to illumos
  • Two diverging versions of IPS (with OI and OmniOS), but only two directories are a problem.
    • Dependency trees wouldn’t resolve
    • Rust version is on the backburner - as it was figured out what the slow issue was in IPS
    • can’t have multiple dependency trees within the same IPS package
      • could potentially put the packages in another location but that often breaks the build tool (typically has to rely on the default location)
  • Someone would like to see Xorg and Mesa updated to the latest
  • Building packages: https://docs.openindiana.org/dev/userland/
  • Developing drivers (book): https://illumos.org/books/wdd/bookinfo.html#bookinfo
    • ARM drivers might be the easiest to work on
    • Rust drivers
      • Some in helios gate - illumos-gate repo at oxide should have some experiments
        • Network driver and network fastpath driver are written in rust, and can be compiled and run on OI, but the software itself is beta. However, these could be packages.
      • MaxPower experiment (Robert Mustacchi or Rick Lowe - not sure which)
      • use Rust no-std environment
      • use prepared kernel functions
      • write safe Rust functions as FFI to unsafe C kernel functions
  • Might be good to incrementally update solaris docs to be OI-specific, and remove solaris docs from search (but still reference them)
    • Legacy consolidation could probably be deleted completely
  • Oxide didn’t really like gmake, contributing to Oxide choosing dmake builds in OmniOS
  • KaOS is mentioned as a linux distro that might want to switch to illumos, but it is also mentioned this would likely be very difficult. It would be good to coordinate.
  • For Rust dev on OI, https://helix-editor.com/ works and supports rust-analyzer and debugging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment