Important changes to 32bit Porteus
Posted: 08 Dec 2012, 19:54
The decision has been made to move away from the Trinity desktop as default for the 32bit version of Porteus. This decision in no way reflects the development of, or detracts from the quality of the Trinity Desktop Environment project. Those guys do a great job. The decision was made for the following reasons:
1) The move from qt3 to a tqt3 wrapper means many of the older kde3 applications will not compile under the TDE environment. This limits choices of applications for our users.
2) As TDE is still in development each new release brings new bugs for us. This again is not a reflection of the quality of development but rather a combination of Porteus being a stripped version of Slackware and Trinity being an ever changing and evolving environment. The latest bug that affected Porteus proved to be a show stopper.
As maintainer of a distro we must think to the future and for this reason i have decided to go with razorqt as the default desktop for Porteus 32bit. This will bring in qt4 which opens up a plethora of available applications and accommodates the use of many of the applications available to the 64bit version. Razorqt is a fast lightweight desktop environment which still allows support for legacy machines and runs insanely fast on newer hardware.
Lxde will also be dropped from the lineup as it really makes no sense to have 2 lightweight desktops in the one distro. The lxde desktop will be available for download via the menu in the final version. These decisions culminate in the addition of many more applications to the default iso while still remaining below the 300Mb theoretical benchmark we aim for (in fact it is only 229Mb so far).
No doubt there will be disappointed Trinity fans and those users are welcome to pickup maintenance of the TDE module where i left off. I can provide compilation instructions and scripts for those interested. The move also means that the unofficial 32bit KDE4 Porteus can run along side Razorqt and share many of the same applications.
I wanted to notify Porteus users of the changes as we consider this a community distro and while the above decisions are final, we would welcome any suggestions, constructive opinions and/or volunteers to maintain a Trinity module.
1) The move from qt3 to a tqt3 wrapper means many of the older kde3 applications will not compile under the TDE environment. This limits choices of applications for our users.
2) As TDE is still in development each new release brings new bugs for us. This again is not a reflection of the quality of development but rather a combination of Porteus being a stripped version of Slackware and Trinity being an ever changing and evolving environment. The latest bug that affected Porteus proved to be a show stopper.
As maintainer of a distro we must think to the future and for this reason i have decided to go with razorqt as the default desktop for Porteus 32bit. This will bring in qt4 which opens up a plethora of available applications and accommodates the use of many of the applications available to the 64bit version. Razorqt is a fast lightweight desktop environment which still allows support for legacy machines and runs insanely fast on newer hardware.
Lxde will also be dropped from the lineup as it really makes no sense to have 2 lightweight desktops in the one distro. The lxde desktop will be available for download via the menu in the final version. These decisions culminate in the addition of many more applications to the default iso while still remaining below the 300Mb theoretical benchmark we aim for (in fact it is only 229Mb so far).
No doubt there will be disappointed Trinity fans and those users are welcome to pickup maintenance of the TDE module where i left off. I can provide compilation instructions and scripts for those interested. The move also means that the unofficial 32bit KDE4 Porteus can run along side Razorqt and share many of the same applications.
I wanted to notify Porteus users of the changes as we consider this a community distro and while the above decisions are final, we would welcome any suggestions, constructive opinions and/or volunteers to maintain a Trinity module.