SliTaz Forum
You are not logged in.
Pages: 1
Hi all SliTaz users and developers!
I know, developers is a sort of strange creatures. Because I'm one of them 
I have a lot of unfinished projects, and hate to write docs…
Now I want to share one of my projects. And I will be happy if one of SliTaz developers will integrate it to the SliTaz web site. I can't finish it, again, sorry.
I hear the same questions here on the forum again and again. What's new in the next Rolling ISO? Do I need to download it? Oh, it's a hard question. Maybe, few upgraded packages, or something else.
See the "kitchen".
All changes are documented. You can see them here: http://hg.slitaz.org/wok
Please, read commit's captions, review diffs, and voilà!
But… Maybe… Oh, shi…
Do you want to know not all changes?
But only changes in the ISO packages? Is it hard?
Ok. I spent my evening in the my most lovely work — coding.
I wrote not-so-big and not-so-small shell script that can answer your question: “What's new?”
Please, open network folder: http://people.slitaz.org/~lexeii/whatsnew/
Download file [c]whatsnew.sh[/c], put it to [c]/usr/bin/[/c] or to your [c]~/.local/bin/[/c] as you wish. Make it executable.
Next, I recommend you to save about 300MB of traffic. Your traffic, and our server traffic.
You need to prepare working directory for this script. Make new folder [c]/home/tux/revs[/c]
Script can make it, but better if you prepare it by your hands. Download to this folder the database [c]all.revs[/c] from my network folder. File size is 1.7MB, and it will save a lot of traffic.
By the way, you can change working folder via editing the 7th line in the script:
[c]WORKING="/home/tux/revs"[/c]
Now you can run the script. Just without arguments: whatsnew.sh
You'll see few new files in the working folder:
[*]packages.list — list of SliTaz Core ISO packages (102 items);
[*]packages.full — the “real” list of packages. It just the packages.list extended with all the packages dependencies (152 items);
[*]packages.info — it is a modern format of TazPkg database, we need it to resolve packages dependencies;
[*]all.revs — the old one. It contains records for all changes in the wok from beginning of SliTaz!
Script can't upgrade packages.list, packages.info, and packages.full. It knows nothing if it works with updated or outdated files. But if you remove these three files (please, don't touch fourth file, all.revs), then it downloads/creates them for you.
And finally! To answer the question “What's new?” we should compare the two states. Compare what and what?
Every wok commit has a number. When I writing these lines, current wok number is 17794 (Wow! So many changes!) Next change will be #17795, etc. Then, new packages are prepared. And then new ISO is builded from these packages.
I have no real numbers, sorry. Our last ISO dated as 1st March. Seems like, when it builds, wok has number 17702. And now wok has number 17794.
Ok, now we have two numbers, two states, and now we can compare them:
[c]whatsnew.sh 17794 17702[/c]
Result is a file report-17702-17794.html you'll find in the working folder.
Right now you can see it: report-17702-17794.html (from my network folder).
Does it answers a question?
Yes, or no, or… maybe?
Ok, it is a semi-automated way (and I hope, it will be full-automated one day).
But, if we want to see more “humanized” reports, then we need a man who will write that reports. Now I see no one around. And I hope that I've found not bad answer to given question.
Offline
Nice work, many thanks!
Offline
Hi llev,
Thank you for your feedback!
Now I realized my next steps.
[*]make a package;
[*]add it to cookutils as dependency, edit cookutils to run whatsnew before/after ISO creating (we need to track current and previous wok revision numbers);
[*]install whatsnew package to cooking environment;
[*]add to cook.slitaz.org ability to show changelogs (I think I can edit them slighty);
[*]add link into main SliTaz web site.
Seems not too hard
Oh, and I need to rewrite script a bit to check not only dependencies of packages, but dependencies of dependencies too, and so on.
Offline
It's very good!
We can have it on mirror with rolling ISO.
And more like daily report.
Offline
Good work, Aleksej!
It can not imagine how it would be in the final form but I am sure it can be useful(already) to show to users that Slitaz is always receiving improvements.
Offline
Charging the SliTaz Rolling is very fast and no break here. Running on USB is more stable and robust. Without fail here too. Congratulations to the development team.
- Leonardo Laporte
- holkfoor | hackdorte
Offline
So folks,
Whats new with Slitaz, Guidelines, announcement, difficulties, collaboration with other little linux distributions ? Will you fix a limit on the expanding of the number of packages ? Can you draw a circle and define the core of Slitaz ? Lots of packages, lots of WebBrowsers, lots of mediaplayers .. but lots of missing lib modules each time. I just recall that for newbies (like me not so long time ago) that a .desktop not working means that Slitaz doesnt work. I'm really glad that Aleksej made Slitaz NexT but why the dev team just dont stop work around the old Slitaz to work only on Slitaz Next ? I know that Slitaz is not made for newbies, but on the other hand, only experts are eager to spend time playing on the code to fix things to make it work on their very old laptop. So why dont leave the old Slitaz as it is and just realise that huge majority of people (even in Slitaz community) just want to have SLitaz work on their middle age laptops (Intel Core 4th Generation to 6th).
To put Slitaz back in the run, would it be possible to ask help or just copy / merge Slitaz with parts of another distro ?
Ofc, i have maybe no idea what im talking about, but i know SLitaz since version 1.
because next is not yet ready....
http://forum.slitaz.org/topic/my-struggles-with-next-/page/2
and its better to have old slitaz updated, than nothing.....
Offline
Hi 
I use SliTaz on 2 old computers (my laptop Asus Eee PC 900 and the desktop computer of my parents).
In my opinion, SliTaz is the only GNU/Linux distribution that we can use on OLD computers without (too many) problems (e.g. (X)(L)Ubuntu is too heavy and… I dont' like Puppy).
So, I would not be very happy if the dev team stops to work on the 32-bits version…
Offline
Pages: 1
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]