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
Affiliation with ExpidusOS? #32019
Comments
No, whatsoever,
@RossComputerGuy is there,
I don't trust his work ;) |
Why are we closing this? I think it can be beneficial to work together to support more devices for Void Linux. |
Reopen as your will. |
Void already supports the Pinephone. Other devices would probably have only 1 user and might require some device specific packages (custom kernel, uboot, etc.), so including them in Void wouldn't make much sense (even the Pinephone kernel in repositories is old). Having those packages in a separate repository like what ExpidusOS does would make more sense, but:
There are people interested in Void on a Pinephone, I know at least about @jcgruenhage and me, git log will probably tell you more. I have some updated packages in my own repository (the pinephone kernel, phosh, squeekboard...), but I wasn't able to properly test them yet, so I didn't make a PR. |
ExpidusOS has different goals than Void Linux. Void is only used as it's design is easier for cross compiling. More devices are supported because the OS is meant to support phones and desktops. Void is primarily a desktop OS. ExpidusOS also ships with a minimum set of packages in the repository because it is expected that users will use the application marketplace. A good analogy is Debian vs Ubuntu with their goals and intended users. |
Neither party is interested, closing thread. |
Hey,
I've come across https://expidusos.com/ while looking for PinePhone distros and wondered if we have any affiliation or connection to the project?
Maybe its worth contacting the project team and talk about hardware support, since that project plans to target more devices in the future?
https://wiki.expidusos.com/index.php/Supported_Devices
The text was updated successfully, but these errors were encountered: