feat: MultiDistribution support #401

Open
opened 2023-11-20 12:37:02 +01:00 by Dedoque · 6 comments
Dedoque commented 2023-11-20 12:37:02 +01:00 (Migrated from github.com)

With os like arch linux installation is impossible becouse apt hardcoded in unreadable scripts.

Describe the solution you'd like

I suggest to use for install system dependencies some one of scm, like Ansible or Salt-ssh.
Described onece -- for many distribs -- Ded/rhel/arch and bsd systems. Simply conditions for different packages and many other features has suppor from box!
No needs difficult bash scripts -- Unreadable, difficult to maintain -- Blood from the eyes!

Describe alternatives you've considered

No response

Additional information

No response

### Is your feature request related to a problem? Please describe With os like arch linux installation is impossible becouse apt hardcoded in unreadable scripts. ### Describe the solution you'd like I suggest to use for install system dependencies some one of scm, like [Ansible](https://docs.ansible.com/ansible/latest/getting_started/index.html) or [Salt-ssh](https://docs.saltproject.io/salt/user-guide/en/latest/topics/salt-ssh.html). Described onece -- for many distribs -- Ded/rhel/arch and bsd systems. Simply conditions for different packages and many other features has suppor from box! No needs difficult bash scripts -- Unreadable, difficult to maintain -- Blood from the eyes! ### Describe alternatives you've considered _No response_ ### Additional information _No response_
dw-0 commented 2023-11-22 09:20:37 +01:00 (Migrated from github.com)

Thanks for the request. A feature like this would likely mean, that there is more maintenance involved with dependencies. Currently dependencies are simply read from the official install script of klipper for example. Thats written with debian based systems in mind. But as im currently working on a rewrite of KIAUH in python, we could think about a different, a new approach of handling each components dependencies to allow other distros. This would also result in much more testing though. I have added the feature request to the "next" milestone. For now it will not be part of the v6 release.

Thanks for the request. A feature like this would likely mean, that there is more maintenance involved with dependencies. Currently dependencies are simply read from the official install script of klipper for example. Thats written with debian based systems in mind. But as im currently working on a rewrite of KIAUH in python, we could think about a different, a new approach of handling each components dependencies to allow other distros. This would also result in much more testing though. I have added the feature request to the "next" milestone. For now it will not be part of the v6 release.
Dedoque commented 2023-11-25 13:42:51 +01:00 (Migrated from github.com)

is more maintenance involved with dependencies.
Based deps: Python and git at all!
Scm just a method of maintaince configuration and state of system.

Thats written with debian based systems in mind. But as im currently working on a rewrite of KIAUH in python, we could think about a different, a new approach of handling each components dependencies to allow other distros.
Same, but little-a-bit simply, maybe. Look at poetry depends and script manager,
and click cmd interfacer.

Do not make a new bicicle, maybe some one already make it))

>> is more maintenance involved with dependencies. Based deps: Python and git at all! Scm just a method of maintaince configuration and state of system. >> Thats written with debian based systems in mind. But as im currently working on a rewrite of KIAUH in python, we could think about a different, a new approach of handling each components dependencies to allow other distros. Same, but little-a-bit simply, maybe. Look at [poetry](https://python-poetry.org/docs/) depends and script manager, and [click](https://click.palletsprojects.com/en/8.1.x/) cmd interfacer. Do not make a new bicicle, maybe some one already make it))
dw-0 commented 2023-11-25 15:45:10 +01:00 (Migrated from github.com)

I want to stick to the python standard library and don't want KIAUH to have special python dependencies.
The most complicated part of the TUI is already rewritten :)

I want to stick to the python standard library and don't want KIAUH to have special python dependencies. The most complicated part of the TUI is already rewritten :)
Dedoque commented 2023-12-01 00:47:06 +01:00 (Migrated from github.com)

don't want KIAUH to have special python dependencies.
<< that's right!
And there is no need for this!
Keep it up!
We wait!

>>don't want KIAUH to have special python dependencies. << that's right! And there is no need for this! Keep it up! We wait!
BiloxiGeek commented 2024-01-17 16:01:14 +01:00 (Migrated from github.com)

Is there any sort of timeline on the python V6 release?

I started looking deeper into kiauh to see if I can get it working on an rpm based system, specifically Alma Linux but that would mean the popular rpm based distros would likely work as well. I'd rather not spend the time digging that deep into kiauh if the rewrite is in the works and coming soon.

I got a fairly high amount of experience with RHEL style systems and I'm willing to help test the rewrite.

Is there any sort of timeline on the python V6 release? I started looking deeper into kiauh to see if I can get it working on an rpm based system, specifically Alma Linux but that would mean the popular rpm based distros would likely work as well. I'd rather not spend the time digging that deep into kiauh if the rewrite is in the works and coming soon. I got a fairly high amount of experience with RHEL style systems and I'm willing to help test the rewrite.
dw-0 commented 2024-01-17 17:21:14 +01:00 (Migrated from github.com)

Hi @BiloxiGeek ,
currently there is no ETA for a possible release. The current development still focuses on debian based systems as well, i have not added any generic "use package manager x now" functions implemented. The current state is, that the regular "klipper stack" is working. That means installation, updating and removing of Klipper, Moonraker and currently only Mainsail. Fluidd will follow next probably. All other features are still in the pipeline. So i would not use the term "soon" at the moment, im sorry.

Hi @BiloxiGeek , currently there is no ETA for a possible release. The current development still focuses on debian based systems as well, i have not added any generic "use package manager x now" functions implemented. The current state is, that the regular "klipper stack" is working. That means installation, updating and removing of Klipper, Moonraker and currently only Mainsail. Fluidd will follow next probably. All other features are still in the pipeline. So i would not use the term "soon" at the moment, im sorry.
Sign in to join this conversation.