-
Notifications
You must be signed in to change notification settings - Fork 791
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
Readme update #1514
Open
OctopusButtons
wants to merge
63
commits into
libretro:master
Choose a base branch
from
OctopusButtons:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Readme update #1514
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
WIP documentation NOT FINISHED YET
Including broad breakdown into all general details and then Maintenance / Technical Usage admin ops. WIP research into each sub-database.
Key Field CRC vs Serial
WIP per dat descriptions (non-exhaustive).
WIP updates
Contributions draft etc
New explicit note about how thumbnail names (and therefore thumbnail assignment) aren't synced to database name changes. I'm partly mentioning for people investigating database/thumbnail troubles, but also to maybe get the interest of a volunteer someday.
Adding brief troubleshooting section
Moved out tentative "Troubleshooting" to new draft Docs site databases.md
Wow, that's quite complete :) |
zoltanvb
reviewed
Jan 21, 2025
zoltanvb
reviewed
Jan 21, 2025
Fixed link to master, was wrongly linked to a specific history/commit
Changed wording about header `name` to fix the wrong statement/generalization pointed out by reviewer. Name isn't always `manufacturer - system`, and core info files (now linked) detail what it should be.
Extra clear about the `database` field in .info files now
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you to @RobLoach, @zoltanvb, @hunterk, @zach-morris, i30817, for helpful information, answers, and discussions.
Database readme update.
Goals
description
header in particular, in the hopes of addressing sourcing mysteries for future or current dats.List of Additions / Expansions
.dat
and.rdb
filesdescription
field and the current or systematic lack of sourcing/documentation for several dats. Intended to address the situation where, I believe, many people see a typical headerdescription "Manufacturer - Console"
and mistakenly think that's required for functionality/by-spec. Specification now given about better documentation of origins, sourcing, including both upstream credit and contributor/scraper/builder and the purpose of the dat if applicable (i.e. what niche or subset or games)/dat
versus in/metadat
, partly covers questions of whether a dat is ad hoc / contribute-able Versus whether it's bulk-overwritten by imports, in order to assist/encourage contributions.