undoIT wrote:How about a semi-rolling model so that not every package that comes down the pipe is upgraded but certain mile-stones or at certain intervals...
This is model of Linux Mint Debian Edition.
undoIT wrote:How about a semi-rolling model so that not every package that comes down the pipe is upgraded but certain mile-stones or at certain intervals...
ferri wrote:undoIT wrote:How about a semi-rolling model so that not every package that comes down the pipe is upgraded but certain mile-stones or at certain intervals...
This is model of Linux Mint Debian Edition.
undoIT wrote:Yeah. I just wish there were more focus on KDE for LMDE. There were discussions about that a while back, dropping Mint KDE and moving KDE to LMDE, but then they went ahead with a Mint KDE release for version 12. Now that they are focusing on Cinnamon and Mate, I doubt KDE is going to get the attention it deserves for LMDE.
undoIT wrote:ferri wrote:This is model of Linux Mint Debian Edition.
Yeah. I just wish there were more focus on KDE for LMDE. There were discussions about that a while back, dropping Mint KDE and moving KDE to LMDE, but then they went ahead with a Mint KDE release for version 12. Now that they are focusing on Cinnamon and Mate, I doubt KDE is going to get the attention it deserves for LMDE.
ruel24 wrote:Since Mint KDE is based on Kubuntu, and Kubuntu is officially dead, there definitely won't be a Mint KDE edition. KDE will have to move back to LMDE unless they want to maintain their own, which I doubt they will given Cinnamon and MATE. Mint is an awesome distro that's hampered with goofy Gnome. Mint KDE is nice enough, but like Kubuntu, a red headed stepchild of the main Gnome release. Personally, I'm disappointed by that. I'll never use anything but KDE. I just can't stand to use stripped down/dumbed down desktops.
ghmitch wrote:For example, I am thinking that if ALL of the "sys v init" packages had been managed under a "task-sysvinit" meta package, it would save having to deal with each sys v package individually in the transition to systemd. Instead, the upgrade would be handled by removing one package "task-sysvinit" and installing one package "task-systemd".
In order to satisfy the 'systemd-sysvinit|sysvinit-legacy|sysvinit-legacy|systemd-sysvinit' dependency, one of the following packages is needed:
1- systemd-sysvinit-44-13.mga2.x86_64: System V init tools (to install)
2- sysvinit-legacy-2.87-17.mga2.x86_64: Programs which control basic system processes (to install)
What is your choice? (1-2)
doktor5000 wrote:It can't be made simpler than that, without leaving user still a choice for SysV or systemd.
ghmitch wrote:Right now, Mageia seems to be holding a lot back in Cauldren, because what is finally coming through in Mageia is rock solid. I DO NOT WANT TO SEE THIS CHANGE.
Return to General discussions about Mageia
Users browsing this forum: No registered users and 1 guest