Created attachment 162863 [details]
RetroArch (also known as libretro implementation) is the lowest tier of the entertainment platform aiming to play older computer games, videos, and other multimedia content.
Many so-called cores are available for RetroArch, that are able to play games and other content. (one example is https://github.com/Themaister/Dinothawr)
RetroArch/libretro also has the vibrant and growing community of game lovers. Many, if not all those games can play on FreeBSD, even though they were originally designed for various other platforms.
Created attachment 162893 [details]
Created attachment 162895 [details]
See also the core pack for RetroArch: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204452
@Yuri, bugzilla will automatically link correctly to the appropriate issue if you use 'bug <id>' in your comments. If you could also use the the following issue fields instead of comments to denote issue relationships, it will ensure things don't get lost/missed/forgotten/committed incorrectly:
Depends On: List of issues that must be committed before this issue.
Blocks: List of issues that cannot be committed/resolved before this issue
See Also: List of issues that are related/similar but not the same as this issue
I have replaced bug 204379 with bug 204452 as the blocking issue for this one based on my current understanding, since bug 204379 was closed 'overcome by events' it cant be a blocker. If this is incorrect, please update the fields so that they reflect the relationships correctly and completely
Except they aren't blocking each other. They are related, but not set to be dependent on each other. This is why I only added a "see also", and not a dependency.
To use RetroArch people for now just need to install both ports.
(In reply to yuri from comment #5)
Case in point (my misunderstanding) why it's important that issue reporters set these fields themselves.
Bug 204452 wasn't set in See Also:, setting that now.
test-builds done on 11-amd64, 10.2a+i, 9.3a, all fine
@Kubilay Just to clarify: the reason they aren't made dependencies of each other is that RetroArch builds roughly 50 times faster compared to the core pack. Also core pack has different platform availability: it is only for 10.X+ and only for amd/i386. It "might" build on 9.X, but somebody should verify this, and I also don't see that it is important to have it run on 9.X.
A commit references this bug:
Date: Sat Nov 14 13:51:28 UTC 2015
New revision: 401567
New port: games/retroarch
RetroArch is the reference frontend for the libretro API. Popular examples
of implementations for this API includes videogame system emulators and
game engines, but also more generalized 3D programs. These programs are
instantiated as dynamic libraries. We refer to these as "libretro cores".
Submitted by: firstname.lastname@example.org