Feature Description
Hey, a few weeks ago you submitted the info file and recipes to our libretro-super repo, which is a necessary step since that's where the info files live and a number of users still use the super scripts to build locally, but we no longer use libretro-super for the CI system that populates RetroArch's core downloader. If you're interested in getting it on the core downloader, we would need a gitlab recipe in the top level of the repo, like this one (from doukutsu-rs-libretro): https://github.com/DrGlaucous/doukutsu-rs-libretro/blob/main/.gitlab-ci.yml
Problem Statement
While rustyNES is integrated with the libretro-super scripts, it won't appear on RetroArch's core downloader unless/until it's added to our current CI pipeline.
Proposed Solution
Add a CI recipe for compatible platforms and we'll handle the rest on our end.
Alternative Solutions
There are some other ways we can tackle it if having the recipe at the top level of the repo is a problem. I didn't see any existing ci-gitlab.yaml recipes, though, which is usually what necessitates this sort of thing.
Use Cases
This would make the core available from within RetroArch, which is how most people find libretro cores.
Impact
Who would benefit from this feature?
Implementation Considerations
Just make sure you only include platforms that will build successfully. That recipe I linked should be a good indication of where we have rust toolchains available.
Reference Examples
I think the one I linked is the best example, but there are a few other rust-based cores that you could look at, as well.
Roadmap Alignment
Where does this fit in the development roadmap?
Additional Context
Any other information, mockups, diagrams, or links that help explain this feature.
Checklist
Feature Description
Hey, a few weeks ago you submitted the info file and recipes to our libretro-super repo, which is a necessary step since that's where the info files live and a number of users still use the super scripts to build locally, but we no longer use libretro-super for the CI system that populates RetroArch's core downloader. If you're interested in getting it on the core downloader, we would need a gitlab recipe in the top level of the repo, like this one (from doukutsu-rs-libretro): https://github.com/DrGlaucous/doukutsu-rs-libretro/blob/main/.gitlab-ci.yml
Problem Statement
While rustyNES is integrated with the libretro-super scripts, it won't appear on RetroArch's core downloader unless/until it's added to our current CI pipeline.
Proposed Solution
Add a CI recipe for compatible platforms and we'll handle the rest on our end.
Alternative Solutions
There are some other ways we can tackle it if having the recipe at the top level of the repo is a problem. I didn't see any existing ci-gitlab.yaml recipes, though, which is usually what necessitates this sort of thing.
Use Cases
This would make the core available from within RetroArch, which is how most people find libretro cores.
Impact
Who would benefit from this feature?
Implementation Considerations
Just make sure you only include platforms that will build successfully. That recipe I linked should be a good indication of where we have rust toolchains available.
Reference Examples
I think the one I linked is the best example, but there are a few other rust-based cores that you could look at, as well.
Roadmap Alignment
Where does this fit in the development roadmap?
Additional Context
Any other information, mockups, diagrams, or links that help explain this feature.
Checklist