Change of Plan: MX Moksha 23.6 Released!

[AVLinux]

hi. i have been running with the RC2 for a bit now, and ive got to say that im impressed. i used mint for a decade, then i tried ubuntu studio for a couple years. then i fully switched to using av about a year or so ago. this is a great middle ground OS that offers mostly out-of-box usability without all of the fluff. for me, your moksha build feels like the first time i havent had to spend a few hours with a new install just removing all the crap i dont need/use. thank you for continuing to develop this very lean system. i look forward to giving 23.6 a go. i will crawl back into the forest in which i dwell now. thanks.

Thanks, that's nice to hear!

[blast0id]

I don't recall what I did, but I was able to log in and do an install. I put in my own password during the install and it's working.

maybe you forced a new password from grub menu > advanced options... I do this sometimes and forget I've done it... derp!

[blast0id]

This probably isn't the place to ask, but I'm just curious if an AVL/Moksha users also use the "User Installed Packages" tool... if so, my question is, do you know if the list created is software version agnostic, and you can use the list created on any future versions of MX linux, as long as there is a version in the repo that has been updated to work with the current version of MX? I'm sorry if this is a confusing question... just curious... seems very helpful for moving from one major release to the next major release...

[AVLinux]

This probably isn't the place to ask, but I'm just curious if an AVL/Moksha users also use the "User Installed Packages" tool... if so, my question is, do you know if the list created is software version agnostic, and you can use the list created on any future versions of MX linux, as long as there is a version in the repo that has been updated to work with the current version of MX? I'm sorry if this is a confusing question... just curious... seems very helpful for moving from one major release to the next major release...

Hi,

Although I'm aware of the tool I don't know it in depth. If it uses Package names without the specific version information then it will definitely be helpful for what you ask...BUT... When you move to a new Debian platform some Package names will change and some packages with be obsoleted or renamed. As an example some names are suffixed with a number so if Debian Bookworm has 'libfunnyface2' and the next Debian moves to 'libfunnyface3' then the User Installed app will likely miss that. Another thing that often happens is a name change or a individual program gets merged into another project, this happened in Debian Trixie with 'samplerate-programs' which is used in AV Linux utilities, it is now part of libsndfile and is called 'sndfile-tools', that would also get missed. The User Installed Packages script is primarily useful for working within the same Distro Release Version going from one machine to another, it gets complicated jumping from an older version to a new platform version.

Most of the tedium in preparing a new Distro release is figuring out the details of package versioning and renaming and updating your build system to accommodate all those new changes..

[blast0id]

The User Installed Packages script is primarily useful for working within the same Distro Release Version going from one machine to another, it gets complicated jumping from an older version to a new platform version.

As always thank you for your time & consideration... finally got your mx moksha installed, had zero of the issues I had with enlightenment when trying to bring over live environment changes after install... also feels noticeably snappier! would love for this to become an AVL base release, if not a full AVL release! I hope I'm one of many monthly donars, because this is certainly a worthy cause, even if only covering a 6pack or so

_blast0id

[asqwerth]

.... The User Installed Packages script is primarily useful for working within the same Distro Release Version going from one machine to another, it gets complicated jumping from an older version to a new platform version....

It's still a pretty good starting point when you move to a new release/version. And for most run of the mill applications, the likelihood of packages being renamed is less, IMO.

Although, UIP probably won't be as helpful for your AV-focused releases with so many proprietary plugins and apps that don't originate from any repos.


BTW, I downloaded your iso to test live and then installed it. It looks awesome, but I have to admit I'm really not familiar with Enlightenment/Moksha, and it's been overlooked in the midst of working on MX25. I think I only booted into it once after installation.

[AVLinux]

The User Installed Packages script is primarily useful for working within the same Distro Release Version going from one machine to another, it gets complicated jumping from an older version to a new platform version.

As always thank you for your time & consideration... finally got your mx moksha installed, had zero of the issues I had with enlightenment when trying to bring over live environment changes after install... also feels noticeably snappier! would love for this to become an AVL base release, if not a full AVL release! I hope I'm one of many monthly donars, because this is certainly a worthy cause, even if only covering a 6pack or so

_blast0id

Thanks I'm glad to hear that! Unfortunately folks like you are quite rare and as a result quite precious, thanks very much! I have a LOT of work to do on AVL 25 but my current plan is to continue with the 'Greatest Hits' type of concept on Enlightenment and something similar with MX Moksha so you will have a choice of either or both..

@asqwerth

Yes, you are correct, another wrinkle is all of the AVL custom packaging is not handled at all by the UIP application.