[mingcongbai]

I mean, it's not required per se, it's right there in a repository... the script configures the repository and installs oma afterwards (there are system dependencies).

https://repo.aosc.io/oma/

Out of curiosity, how - by your preference - should this be done so that it's easier for the user?

[TheDauthi]

Not the original person, but I'd like to see the ACTUAL install instructions, a la the vscode via the microsoft repository. It's a little more work for the user, but, honestly, the user is using a CLI for managing packages - I think three lines that show clearly what's going on is reasonable.

something like:

  curl -fsSL https://repo.aosc.io/pubkeys/repo/oma.gpg | sudo gpg --dearmor -o /usr/share/keyrings/oma.gpg
  echo "deb [signed-by=/usr/share/keyrings/oma.gpg] https://repo.aosc.io/oma $(lsb_release -sc) main" | sudo tee /etc/apt/sources.list.d/oma.list > /dev/null
  sudo apt update && sudo apt install -y oma

Just showing me what it's gonna do and giving me the clear option to do that instead of curl | bash would make me feel better.

Microsoft also has a "download deb and install", which I still consider slightly better than curl | bash; it's basically the windows install flow. People who are using a GUI can just double click it, people who want to see what it's going to do can examine it, and your (unsafe) one-liner is `curl XXX.deb && dpkg -i XXX.deb`. Plus it can be shipped to a multiple machines at once easily.

And hey, you already know they have dpkg.

(edited: mangled my command spacing a bit)