Hi llev,
Let me answer your question.
When you visit aforementioned page ( http://hg.slitaz.org/slitaz-base-files/rev/e9258bc4e858 ) and point your mouse over "Download tarball: bz2 gz" links (4th line from very top) you'll see download links:
http://hg.slitaz.org/slitaz-base-files/archive/e9258bc4e858.tar.bz2
Note changeset is:
slitaz-base-files changeset 265:e9258bc4e858
So, you can download any changeset (any state in the time of particular Hg repository).
Also, you can use short changeset number (265 here):
slitaz-base-files changeset 265:e9258bc4e858
http://hg.slitaz.org/slitaz-base-files/archive/265.tar.bz2
You'll get the same changeset.
And, of course, you can download some "selected" changesets:
http://hg.slitaz.org/slitaz-base-files/
like 5.6.5, 5.6.4 (small gray numbers).
http://hg.slitaz.org/slitaz-base-files/archive/5.6.5.tar.bz2
So, we can use any form of changesets in the SliTaz receipts: long number, short number, or tag.
Next. If you asked me, why I used short changeset number instead of tag, I answer you. There are several reasons.
- Tagging some changeset is a changeset too. It is make a visual mess if tagging is frequent.
- What tags (read: versions) mean? That we make a steps forward, of course. But, how should I name version next to 5.6.4? Maybe, 5.6.5, or 5.7, or 6? I don't know. We have no detailed roadmap to versions release.
- It is a simple bugfixing.
I should say, that it is not completely tag/version drop in the receipts. But I'll found it very handy to update packages receipts after bugfixing, or after implementing important feature.