Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

MAME dat scanning has confusing and inconsistent labels, files, documentation [mixture of databases, docs, and front-end]

Aperta
  • Qualcosa non va?
#1,741 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
30/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
databases, documentation

Direzione di ricerca

The issue mixes three threads: which MAME XML DAT belongs in metadat/mame in libretro-database, the RetroArch front-end help text for the Arcade DAT import options, and the arcade getting-started docs. Start by reading the metadat/mame directory and the linked docs page, then confirm which parts are repo content and which live in the front-end. Done means a documented decision on which MAME XML is hosted and the docs or help text updated; the maintainer has not yet settled the hosting question.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

This issue is a combined mixture of databases, front-end, and documentation. I plan to fix with some future PRs, but I'm opening this for visibility or in case anyone else wants to contribute.

BACKGROUND
I was confused about MAME scanning with a data file. (And I think it's not entirely my fault as a user!)

DETAILS

In cases where a point below may seem itself confusing on my part...sorry!

  • Database file confusion:
    • There's no "current" (post "2016") MAME .XML on libretro https://github.com/libretro/libretro-database/tree/master/metadat/mame
    • This person has what I think are arcade-only dats but I don't know if just copying a current one over to libretro github is considered acceptable, also the readme isn't clear about what it actually is. Is it acceptable to copy random internet dats (if examined for correctness etc) to libretro repository?
    • Ideally we'd want a copy of the official MAME XML hosted on libretro/RA online update servers, fetched by the front end and placed in a default/set location that would be used when toggled in the MAME Import scan. I.e. it could be updated automatically like anything else, though maybe it's a drawback that the file is relatively large (20 MB compressed). I could never implement this myself though (heh).
    • Official MAME file is not arcade-only, it's everything (I think?), and there's no Arcade-only XML file anywhere on libretro repos, except "2016". More on this below.
  • Front-end language and help text. Note the totality of points below altogether, not any given single point. In the Manual Scanning behavior and menu:
    • [choose/select] "Arcade DAT file" has help text that specifies XML DAT
    • [Toggle on/off] "Arcade DAT filter" doesn't say anything about XML
    • I believe it rejects .dat (I don't just mean extension but file format, of course)
    • Those options refer to "Arcade", but the libretro files are "all" of MAME I think (meaning including non-arcade games?). The only "Arcade-only" reference in the libretro repositories is the MAME 2016 xml file https://github.com/libretro/libretro-database/tree/master/metadat/mame
  • Documentation.

I'm going to look into this and eventually PR for documentation update, and maybe Help Text update for the manual scanner Arcade dat options. As for the files, hosting a copy of the official MAME XML on libretro as an official download, ultimately integrated with online updater, seems straightforward in theory but I don't know (and I certainly couldn't program that).

Lingua principale
Python
Stelle
1.5k
Fork
885
Merge medio
1g 22h
PR unite (30g)
6

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di libretro/libretro-database

Tutte le issue di libretro/libretro-database

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.