Date: Thu, 07 Apr 2022 11:36:42 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 263117] games/libretro: Update libretro meta-port and all libretro ports Message-ID: <bug-263117-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263117 Bug ID: 263117 Summary: games/libretro: Update libretro meta-port and all libretro ports Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: dmenelkir@gmail.com Created attachment 233026 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D233026&action= =3Dedit v1 Ok, I know that this isn't the right way to do, but let me explain. *) Libretro cores doesn't have too much dependencies or store too much file= s, so there's not a really security constrain here *) Said that, it's a lot of libretro-cores that had being updated since the last time I've open the last PR *) There's not a point release of those libretro-cores, so it's fine to upd= ate to the last git commit, and libretro-cores doesn't break other applications (since they're pretty much like a single module used by libretro-compatible applications) I've updated all libretro cores to the last git commit and updated the libr= etro meta to all available ones, so it's easy to test/install just using games/libretro, since all cores are marked as default. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263117-7788>