Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git project labels #2181

Open
LukeShortCloud opened this issue Dec 20, 2024 · 2 comments
Open

Git project labels #2181

LukeShortCloud opened this issue Dec 20, 2024 · 2 comments

Comments

@LukeShortCloud
Copy link
Collaborator

It might be useful to add labels to GitHub Issues to help keep track of issues. Some initial ideas I had were:

  • x86_64, apple, arm, loongarch, powerpc, and risc-v = Mention the CPU architecture.
    • Lots of existing reports for Apple Silicon hardware are instantly solved by using muvm to virtualize a 4K pagesize Linux kernel. We can better track these and work on documentation for them.
  • missing_library_native = (I don't love this long name, by the way). The user needs to install a native library.
  • missing_library_nonnative = The user needs to install a non-native library.
    • This will especially be useful soon as I want to track down and help bundle all of these libraries. Especially for Box32 where getting x86_32 libraries is tricky.
  • opcode and wrapper = A missing opcode or wrapper is needed.
  • epic, gog, and steam = For games, label what store is being used.
  • box64 and box32 = Depending on what architecture of the program a user is trying to use, it either relates to Box64 and/or Box32.
@ptitSeb
Copy link
Owner

ptitSeb commented Dec 20, 2024

sure, why not.

Not sure about steam / epic / gog tho.

@LukeShortCloud
Copy link
Collaborator Author

Epic Game Store might not make sense, yeah, since there's no native support. If someone was using that, I guess the label would be wine.

Steam vs GOG could be good since they both provide native Linux builds for some games. I own duplicates across both. There is drift between many games. For example, Star Wars: Empire at War on GOG.com is 32-bit and has never been updated. The Steam version gets yearly updates (since 2006!) and recently had a major overhaul to a new 64-bit engine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants