Building instructions should reference *this* repo #14
Labels
No Label
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: dahjah/ryujinx-mirror#14
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In step two of the Building instructions in the README, the instructions say to use the command
git clone https://github.com/Ryujinx/Ryujinxwhen they should say to use the commandgit clone https://github.com/ryujinx-mirror/ryujinx.Indeed, and this includes other links/references to the original repository, the
ryujinx.orgdomain, CrowdIn, etc.. As of now, I want to keep as much in-tact as possible (besides stuff that could aid in getting this fork potentially taken down) on the upstreammasterbranch until more info comes out from the original Ryujinx team.. If all else, I can create amirror/masterbranch and set that as the default branch for the repo, until we get said additional info.If we can claim the
Ryujinxscope on GitHub, I am willing to turn this into a complete hard-fork of the original Ryujinx project, and we may be able to attempt to maintain it in some form. Can't guarantee that though!@regginator I don't say this to underestimate but IMO you should not host this on Github nor Gitlab at all. It will be taken down after some days. Same happened with Suyu (Yuzu stripped down basically).
There is always troll people impersonating Nintendo out there. My recommendation is to host it in another git server.
Anyways, here you have more repos of ryujinx mirrored by me: https://git.nadeko.net/Ryujinx_Mirror/ (Ryujinx repo contains the wiki)
(Opps, and sorry for going offtopic with the issue! But I wanted to tell you that so feel free to hide this comment later)
It's entirely possible, though do note that the original Ryujinx organization wasn't taken down via a DMCA request, but a private agreement with the maintainer, @gdkchan. Additionally, Ryujinx is licensed under the MIT license, and if doable I can remove any and all external references to
Patreonand the like to be extra safe. I am also quite hesitant about copying over the old wiki for the same reasons.For now, this repository will primarily serve as a somewhat read-only copy of the original project.
Also, fixed in
c6aa83225e😄