SliTaz Forum
You are not logged in.
Pages: 1
Hi Community,
I open this topic to open survey and feedback of you.
Infact on my head i prefer purpose smooth upgrade from 5.0/cooking to next version, but i would like community opinion.
Two option are available :
- purpose upgrade from cooking to new version
=> use [c]tazpkg up -r[/c] to receive last updates
!! This implied ensure your system have pre requirement to doing smooth upgrade !!
Infact tazpkg need have last feature "upgrade tazpkg first, and core components (gcc-lib-base,glibc-base)"
- purpose reinstall with new version livecd
=> Use "Upgrade" feature on SliTaz Installer to switch on new version
What do you prefer option ? (i plan to post also on Facebook page to inform globally)
Another point i would clarify, asked on other post for "old hardware" support, normally with 5.x kernel branch, support remain, but could be compromise with latest 6.x / 7.x, in this case i keep opportunity to have "legacy" version.
I can't finish post without thank all of you, we can't grow without you.
Offline
For exercise i test "Upgrade" option from slitaz-current-core iso.
=> Upgrade seem ok, but broken grub menu.list 
, few packages installed to test not reinstall for airstrike i understood not available, but abiword available not reinstall but gnumeric, firefox-official reinstalled correctly.
In case for "Upgrade" feature need also work to be smooth.
Offline
I prefer fresh install to ensure clean base system and no remains - these are known to cause strange software issues.
Updating from one release to another is sometimes painful even on big distros.
>"old hardware" support
I think we need to define what does _old hardware_ mean.
Sure, we can go back to 486 times just for fun, but what is the minimal usable system requirements for Linux userspace in 2026?
I haven't seen even Pentium 4 grade office PCs in a while.
Offline
Hi devl547,
Thanks for return.
Infact i agree with it, upgrade release to release n could be really hard also for popular established distro.
Goal to survey it's know if community is ok to reinstall system or would like prefer upgrade it.
For old hardware support, it's true for daily usage 486/586 cpus is not usuable specially for browse on the web, but maybe other usages.
Usage should be defined.
Offline
Hi,
For return see on Facebook, people seem interesting by upgrade version, and other no preference.
Both remain available, for upgrade in place (similar to apt dist-upgrade [example 12 to 13]), i push all necessary patch on cooking, i also set version of tazpkg to 5.4 (with 944 rev, hard to ensure version is last with patch).
If system is fully updated and have tazpkg 5.4, all features are in place.
- Ensure tazpkg upgraded before installed updates or package
- Enure glibc-base, gcc-lib-base upgraded first
- Fetch all updates in cache before doing upgrade
Offline
Hello l'équipe SliTaz,
agree with devl547...
Thanks to all of you
Offline
Begin (locally at moment) to rebuild packages with merged wok (wip).
I would like avoid broken cooking chroot.
I create wok-merge folder
- clone wok-cooking / wok-current
- for each packages on repository (1843), copy folder from wok-current to wok-merge
- build all packages (following my cook-all.sh) and adjust receipt to merge modifs when necessary.
Goal to keep/merge all wok modifications (wok rev 25579-25972, wok-current rev 25579-25838)
Compare to wok with 6000+ packages, impacted packages could be only 1843
[attachment=53930,3844]
Offline
Pages: 1
[ Generated in 0.021 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]