asqwerth wrote: ↑Tue Dec 18, 2018 11:36 am
I don't really consider MX any sort of rolling because the base does not change, and any new packages are not from Debian Testing. MX Test Repo is not Debian Testing. Debian Backports repo is not Debian Testing.
@stevo.... how about calling it a forever release or maybe 'catch & release' (I guess that's a fishing thing.) hmmm.
Pax vobiscum, Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
This website description is based on Distrowatch's description.
My personal view (in the minority of the Dev Team) is that it does not describe MX. Hopefully I'm not hit with a gag order against speaking on this issue again....
What then does "semi" mean in DW's eyes? 2 possibilities:
1) Core packages don't roll, and the rest can be updated (ie, roll) part of the way through backporting, up to a point where it finally hits a brick wall and can't anymore.
2) MX Releases based on the same Debian Base can be "rolled" from the older to the newer release, while those releases based on different Debian Bases can't. This second definition is what MX is using on the MX website.
So I would advise not getting your hopes up for the moment as regards any easy move from MX18 to MX-buster.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400