What do you think about having Slitaz 5RC3 ?
It could be a nice idea, no ?
Slitaz 5.0 RC3
(24 posts) (10 voices)- Started 10 years ago by erjo
- Latest reply from kubepc
- This topic is not a support question
-
erjo
offlineKey MasterPosted 10 years ago # -
Ceel
offlineAdministratorHi erjo,
I agree!
Posted 10 years ago # -
devl547
offline~ # cook my_lifeUpdate toolchain! xD
Man, our gcc and glibc versions are from paleozoic era.Posted 10 years ago # -
kultex
offlineKey Master@erjo - it is really necessary to make quick a RC3, to get rid of RC2
@devl547 - its true that gcc and glibc are quite old, but I think, it would be no good idea to update them or to another kernel - 3.2.x is supported until 2017-04-26
https://www.kernel.org/
https://lkml.org/lkml/2015/1/1/50@all - whats necessary to finish 5.0 ???
maybe we can collect the ideas here - just my thoughts:
1) Update kernel to 3.2.66
2) work on "tazhw setup printer" - thats totally out of order
3) Aleksej worked on tazx, so that tazx detects automatic the grafic chip - my question is I think for Pascal - is it possible to get a bootline, that automatic boots to tazx and installs the correct grafic drivers - of course, if there is internet....
maybe we can collect the issues here and finish 5.0 within a month?
Posted 10 years ago # -
Sidini
offlineMemberI think it's a really good idea to make a RC3, because RC2 is too old and there are some people that still using it. Also, RC3 could increase visits to Slitaz at DistroWatch.
I don't know how Slitaz team develops it, but I suggest to use the Debian style of: unstable (rolling) -> frozen (tests phase) -> stable (RC3 or 5.0).
This can minimize the occurrence of bugs and errors. But, of course, it's just an idea. :DWhat's necessary to finish 5.0? To me, the system is very good. Just make a stable version (without bugs) and I'll be happy. :D
Posted 10 years ago # -
devl547
offline~ # cook my_life>3.2.x is supported until 2017-04-26
Sure, but IMHO new desktop features and bugfixes are more crucial than LTS support for servers.
And also on kernel.org:
mainline: 3.19 2015-02-09
stable: 3.18.7 2015-02-11All other are LTS.
Posted 10 years ago # -
Anonymous
offlineUnregistered... pls, no "automatic" network connections to repositories or anywhere... every network connection should be explicitly requested by the user... thats critical for who does forensics ;)
(... personally, at live boot, I would even remove that dhcp request on LAN... its also useless for who doesnt use wired net, and slows down boot time 4+ secs...)
[... personally, at live boot, also wrong is the automatic wireless modules probe, because sometimes the loaded module is wrong... blacklisting on live is inappropriate and further unloading the module often crashes all... ]
{... FYI, at live boot, the kernel messages get scattered all over the screen, on smaller monitors, e.g. on a netbook pc... }Posted 10 years ago # -
kubepc
offlineMemberSliTaz is a very good distro. My thank goes to all the developers.
I would appreciate a SliTaz 5.0 RC3 version in March 2015.Today I have testet the weekly from the 15th. of Febuary. Unfortunately there are still some disappearing mouse pointers in this version. These bugs should be fixed before releasing RC3. For instance the mouse pointer is disappearing when I move the mouse pointer over the close button in alsaplayer and it is disappearing when I move it over the close button in xine-ui. There it shows the help "Hide Gui", but before that the mouse pointer has disappeared.
The isomaster should be updated and I would wish, that it would be integrated in RC3. At least it should not be forgotten in the locale-xx-extra packages.
Posted 10 years ago # -
Anonymous
offlineUnregistered... agree, mouse pointer which disappears is very annoying also for me... v4 doesn't have this issue, don't see a reason why we should suffer that torture in v5 ;)
Posted 10 years ago # -
Trixar_za
offlineKey MasterIt's a common issue with LXDE based Linuxes. I had a similiar disappearing mouse issue with Ubuntu and Debian. Using a different windows manager apparently fixes the issue because Peppermint didn't have the issue (it uses xfce's windows manager instead of Openbox). Updating the packages to latest versions will probably fix the bug though - so freezing the repository would be a BAD idea right now.
Posted 10 years ago # -
Anonymous
offlineUnregistered... so v5r3 will be fully LXDE?
afaiu, v4 is a mix of openbox + xfce... not bad I would say...
so why now shift to fully LXDE? isn't full LXDE more battery consuming on old laptops? fancy to describe the reasons for that change? ;)Posted 10 years ago # -
Trixar_za
offlineKey MasterI'm saying it's either Openbox or it's interaction with the LXDE components that's causing the issue. It has been fixed in current versions of Lubuntu and LXDE Debian though - it seems like it's an issue from 2013 to mid 2014 and got fixed at some point. So clearly we just need to update the LXDE components (and Openbox) to fix it.
SliTaz 4 uses LXDE's pcmanfm, panel, display and theme manager and choice of windows manager.
Personally, I feel we should be going with a full Qt based version since LXDE and RazorQt merged to form LXQt. It's much lighter on system resources, dependencies and iso size space required than what current LXDE needs. We could then just have the user install GTK with packages that need it (or include it since we'll be saving space from not having to meet pcmanfm's heavy requirements).
Posted 10 years ago # -
Anonymous
offlineUnregistered... oh, LXQt, never heard of it! :) thanks, I went to distrowatch and tried one of the only 2 distro with it... well, boot normal speed, desktop in idle 1% cpu, shutdown 2 seconds (!)... played with openbox and lxqt settings, didnt see much difference, fast as our v4 env, no disappearing mouse indeed, but again pcmanfm errors, couldnt mount my hd partitions...
anyway, looks promising... so agree, just drop out a r3 in lxde+openbox as planned to close that neverending loop... and after we could give a shot to LXQt ... ;)Posted 10 years ago #
Reply »
You must log in to post.
