libretro / libretro/libretro-database
Database for Neogeo/AES
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 877
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 24
Description
Why isn't Neogeo considered a standalone platform with a separate DB?
MAME/MESS considers Neogeo/AES as a separate platform with a separate software list: https://github.com/mamedev/mame/blob/master/hash/neogeo.xml libretro-db could reuse that list.
RetroArch needs a separate database to be able to treat Neogeo as a separate platform and not as arcade games. This will make visualization and configuration easier.
Suggested by @RobLoach in libretro/RetroArch#7287.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the MAME/MESS neogeo.xml software list linked in the issue and the related RetroArch#7287 discussion. Trace how libretro-db represents platform databases, then determine the changes needed for Neo Geo/AES to be separate from arcade games; done means RetroArch can use a distinct database for visualization and configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100