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 whatsnew.sh
, put it to /usr/bin/
or to your ~/.local/bin/
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 /home/tux/revs
Script can make it, but better if you prepare it by your hands. Download to this folder the database all.revs
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:
WORKING="/home/tux/revs"
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:
whatsnew.sh 17794 17702
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.