Re-working the installer #383
alextrical
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@cryinkfly I'm thinking that the installer and repo structure could do with a bit of an overhaul, as the project has evolved quite a bit since its conception.
There are a few things I would like to help with if you are happy for collaboration.
-Change the install GUI to something more like what you are using for Solidworks
-Setup actual branches in GitHub for development (instead of folders in Main)
-Source control as much as possible, and lock scripts to specific versions, instead of referencing the latest files in the Main branch, that may change or be moved over time, we should include as much as possible inside the downloaded script
-Detect the version of Linux in use, and only ask the user if it can't be detected
-Health check of the project, once a report of Autodesk breaking change, let any installers know there are known breaking issues that we are aware of
-Detect version of Wine installed, offer option to install if missing or older than the minimum usable version (8.14)
-Create a branch for a Flatpak version, assuming there is a version of Wine 8.14 or higher available on Flathub. If not then I will compile and host it (probably 9.1) on GitHub, and then figure out if we can pull it from there with a script
let me know what you think, and i can put some time towards the project
Beta Was this translation helpful? Give feedback.
All reactions