Moksha Desktop Environment as optional for MX? Thoughts?
Posted: Fri Feb 02, 2024 3:59 pm
Hi,
For the last month or so I've been experimenting with the Moksha Desktop Environment which is a fork of the Enlightenment E-17 branch and is most notably the attractive Desktop Environment in the popular Bodhi Linux Distribution. Moksha is a bit more refined than Enlightenment and has some improvements and buggy features stripped out. Moksha is also very notable for being super resource friendly while at the same time providing a nicely composited UI experience, it's super light (+/- 200Mb of RAM) on 32bit hardware. Bodhi Linux is actually working on a Debian-based set of ISO's loosely called 'deBodhi' so I have been mixing their Debian sources with MX Linux and some of my own customizations from AV Linux but there are many flies in the ointment (I've been driving poor @dolphin_oracle nuts!). I don't want to reinvent Bodhi, they are doing a phenomenal job on their own! But I do see the potential for a combination of Moksha and the MX Toolset being a very potent mix! I think having clean MX Packaging of Moksha and it's modules would be a much more viable solution than creating a Frankendebian blend of Bodhi and MX.. What I have running as a prototype functions but there is a lot of glue and duct tape involved..
Screenie of prototype: http://bandshed.net/images/screenshots/ ... _07_21.png
Issues encountered with blending deBodhi and MX as separate projects..
- Moksha leans heavily toward systemd, for MX it needs to work smoothly with both sysvinit and systemd
- There are messy Repository conflicts especially with Firmware packages between Bodhi and MX
- PipeWire is a challenge to get working as Moksha currently has a hard dependency for PulseAudio that has to be hacked around.. *fixed
- System power actions (ie shutdown, reboot, suspend) are problematic with sysvinit *workaround being tested
- External disk mounting is problematic with sysvinit.
Interestingly 'Artix' which is an Arch based non-systemd Distro has Moksha and it's modules completely packaged so there seemingly are some ways to get around the systemd reliance..
Packaging Challenges:
- Moksha for MX should probably use the current EFL (Enlightenment Foundation Libraries) libraries in Debian as it's base, Bodhi packages these differently as 'libefl'.
- Moksha would also need it's modules packaged which are modular bits that add various important functions.
- Moksha has several UI themes made for Bodhi that are made to work with it, at least some of them would need to be included and un-branded (I could help with this)
Anyway, maybe this is a ridiculous thing to ask but I thought I'd put it out there and guage what the community interest may be..? As it is on my test bench it's an interesting garage project but not fit to distribute..
Here is the page for Moksha itself but hopefully much of the actual packaging structure and dependency info could be crossported from the 'deBodhi' Repository packaging... I have some skills putting ISO's together but unfortunately I'm not a Coder or good with modifying sources beyond a rudimentary level but I could help with the visual MX-ification or perhaps even better "debranding"
https://www.bodhilinux.com/moksha-desktop/
PACKAGE FOLDER SOURCES: https://github.com/BodhiDev/bodhi7packages
*ADDED NOTES!
Bodhi has a specially patched arandr version which saves the resolution settings directly to Moksha startup, this would be wise to include:
https://github.com/BodhiDev/bodhi7packa ... r/bookworm
For the last month or so I've been experimenting with the Moksha Desktop Environment which is a fork of the Enlightenment E-17 branch and is most notably the attractive Desktop Environment in the popular Bodhi Linux Distribution. Moksha is a bit more refined than Enlightenment and has some improvements and buggy features stripped out. Moksha is also very notable for being super resource friendly while at the same time providing a nicely composited UI experience, it's super light (+/- 200Mb of RAM) on 32bit hardware. Bodhi Linux is actually working on a Debian-based set of ISO's loosely called 'deBodhi' so I have been mixing their Debian sources with MX Linux and some of my own customizations from AV Linux but there are many flies in the ointment (I've been driving poor @dolphin_oracle nuts!). I don't want to reinvent Bodhi, they are doing a phenomenal job on their own! But I do see the potential for a combination of Moksha and the MX Toolset being a very potent mix! I think having clean MX Packaging of Moksha and it's modules would be a much more viable solution than creating a Frankendebian blend of Bodhi and MX.. What I have running as a prototype functions but there is a lot of glue and duct tape involved..
Screenie of prototype: http://bandshed.net/images/screenshots/ ... _07_21.png
Issues encountered with blending deBodhi and MX as separate projects..
- Moksha leans heavily toward systemd, for MX it needs to work smoothly with both sysvinit and systemd
- There are messy Repository conflicts especially with Firmware packages between Bodhi and MX
- PipeWire is a challenge to get working as Moksha currently has a hard dependency for PulseAudio that has to be hacked around.. *fixed
- System power actions (ie shutdown, reboot, suspend) are problematic with sysvinit *workaround being tested
- External disk mounting is problematic with sysvinit.
Interestingly 'Artix' which is an Arch based non-systemd Distro has Moksha and it's modules completely packaged so there seemingly are some ways to get around the systemd reliance..
Packaging Challenges:
- Moksha for MX should probably use the current EFL (Enlightenment Foundation Libraries) libraries in Debian as it's base, Bodhi packages these differently as 'libefl'.
- Moksha would also need it's modules packaged which are modular bits that add various important functions.
- Moksha has several UI themes made for Bodhi that are made to work with it, at least some of them would need to be included and un-branded (I could help with this)
Anyway, maybe this is a ridiculous thing to ask but I thought I'd put it out there and guage what the community interest may be..? As it is on my test bench it's an interesting garage project but not fit to distribute..
Here is the page for Moksha itself but hopefully much of the actual packaging structure and dependency info could be crossported from the 'deBodhi' Repository packaging... I have some skills putting ISO's together but unfortunately I'm not a Coder or good with modifying sources beyond a rudimentary level but I could help with the visual MX-ification or perhaps even better "debranding"
https://www.bodhilinux.com/moksha-desktop/
PACKAGE FOLDER SOURCES: https://github.com/BodhiDev/bodhi7packages
*ADDED NOTES!
Bodhi has a specially patched arandr version which saves the resolution settings directly to Moksha startup, this would be wise to include:
https://github.com/BodhiDev/bodhi7packa ... r/bookworm