Skip to content
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

[Feature Proposal] Rolling release Launcher/installer #126

Open
jurassicjordan opened this issue Nov 4, 2024 · 1 comment
Open

[Feature Proposal] Rolling release Launcher/installer #126

jurassicjordan opened this issue Nov 4, 2024 · 1 comment

Comments

@jurassicjordan
Copy link

jurassicjordan commented Nov 4, 2024

Proposal for an idea on how blazium can be fully rolling release, using a launcher that automatically clones and builds the current state of the dev branch (or selected branch in launcher) and automatically build for user.

What if instead of making a big release, blazium was a rolling release engine. What you could release is a “launcher” that manages versions of blazium, and clones and builds it on the spot when you click install from a list of versions of blazium. Essentially a GitHub GUI but just for blazium that also builds and launches the engine

heres how I envision it:

  • launcher, when freshly installed will give the user options set install, build and project directories
  • launcher will have a 4 tabs
  • I imagine you eventually plan on making a blazium 3.6 branch or something like that, but in the mean time the only option would be to just install 4.3
  • install options would allow you to configure your build, select operating system (default would be current operating system launcher is running on for obvious reasons.
  • install options would then let you choose if you want to choose a location for the binary or to just install to the launcher list (which would be default option)
  • installing to launcher list would clone the selected branch repository to the build folder you selected when setting up the launcher first time. launcher will then preform the scons commands behind the GUI and build blazium, then move the binary to the installs folder, where the launcher will depict it in the installed tab as well
  • from installed branches tab, you can choose to update your installed branches if PRs have been merged, by recloning and rebuilding.

I'm not a programmer, but I know that the main issue with this idea would be dependencies. thats something I haven't thought of yet.
perhapse the launcher can automatically install dependancies, but that would be tough for other devices like android, or even linux, being that every distribution has its own package manager. what are your thoughts on the idea?

@Captain-Wet-Beard
Copy link

Imo the problem this is meant to solve is mostly solved by using another OS. Most operating systems have a software manager to make managing software versions and handling all your dependencies very easy. Windows doesn't really have that, but that's just an inherent problem with Windows specifically.

I use an OS that's based around rolling software releases, so I can often install the fresh git versions of things through my software manager, but I still tend to prefer downloading precompiled binary releases because compiling software is more time consuming for the end user than just downloading the most recent binary release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants