-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Make PolyMC package actually package PolyMC #45292
Comments
sgn
added a commit
to sgn/void-packages
that referenced
this issue
Jul 28, 2023
It's a year since we removed it. Let's be honest and declare that we don't have PolyMC. Close: void-linux#45292
Merged
OK, let's remove that package,so we won't be pulled to that mess. |
sgn
added a commit
that referenced
this issue
Jul 28, 2023
It's a year since we removed it. Let's be honest and declare that we don't have PolyMC. Close: #45292
If anyone is interested PolyMC is now available here: https://xslendi.xyz/void under the name of |
zen0bit
pushed a commit
to oSoWoSo/VUR
that referenced
this issue
Aug 6, 2023
It's a year since we removed it. Let's be honest and declare that we don't have PolyMC. Close: void-linux#45292
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
People have been saying that there has been a takeover. This is blown out of proportion and it's completely false. The maintainer, Lennymclennington was the one who started the project and is, and still is, the original owner. He has every right to do whatever he chooses with his project. Another huge misunderstanding is that he will use the project to spread malware. This came from the fact that he owns the meta servers. He has no grudges against anyone and he's not a serial killer, he just wanted a project that focused on the piece of software itself, not what ideology it promotes. For all the reasons above, I would please request a investigation on the current state of the project and for the package to be back in the repositories again. Thank you.
The text was updated successfully, but these errors were encountered: