libretro / libretro/RetroArch

Feature request: Enhance Core Info Files to include detailed version and build information

Open
#16,684 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Full summary example:

Main Menu -> Information -> Core Information

  • Core Name: PCSX-ReArmed
  • Core Version: [1.0 for example]
  • Core Library Version [renamed from "Core Version"]: r24l 9aefd42
  • Build Date: [YYYY-MM-DD]
  • Git Version: [whatever]

Description

Main Menu -> Information -> System Information is more detailed than Main Menu -> Information -> Core Information

Main Menu -> Information -> System Information has:

  • RetroArch Version
  • Git Version
  • Build Date

Example:
image

Expected behavior
  • Add "Core Version" -- this is useful to make it simple to follow up core bug reports
  • Replace "Core Version" with "Git Version"?
  • Add "Build Date" -- this is useful to make it simple to follow up core bug reports
Actual behavior

image

Steps to reproduce the bug
  • Main Menu -> Load Core -> [Any core]
  • Main Menu -> Information -> Core Information
Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.19.0
Environment information
  • OS: GNU/Linux

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Main Menu -> Information -> Core Information screen after loading any core, then compare its implementation with System Information, which already shows RetroArch Version, Git Version, and Build Date. The work is done when Core Information clearly presents the requested core version or library version, Git version, and build date, with the terminology resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.