SliTaz SliTaz Forum archive

This forum is now a read-only archive

The SliTaz community has moved to Maille, a forum made for SliTaz.

We looked hard for a replacement for this aging forum, including a move from bbPress to FluxBB last June. But spam bots now get through sign-up even with mail confirmation, and these forum engines are barely maintained anymore. So we wrote a forum in the SliTaz spirit: small, fast, no JavaScript, works on old machines and in text browsers. Everything here stays readable.

Go to Maille

You are not logged in.

#1 2020-10-22 01:19:52

Alex-Tony-Sekares
Member
Registered: 2020-10-22
Posts: 1

Meaning and scope of: cooking cross extra get next next64 stable tiny undigest

I want to know what is the difference between the package directories found in the Slitaz mirrors. Could someone explain what "cooking", "cross", "extra", "get", "next", "next64", "stable", "tiny", "undigest" stand for? I searched in the documentation and found no answers. Thank you for your generous help.

Offline

#2 2020-10-31 16:59:48

bellard
Administrator
Registered: 2011-03-28
Posts: 657

Re: Meaning and scope of: cooking cross extra get next next64 stable tiny undigest

cooking: the current version under development (weekly builds in rolling folder).

stable: previous version, frozen.

next: will be the cooking when the cooking will move to stable (32 bits).

next64: same as next for 64 bits cpu.

undigest: removed from cooking because they not work/compile. Need fixes.

extra/get: packages/scripts to get binaries from the web (example skype).

tiny: SliTaz for very old machines see http://tiny.slitaz.org/

cross: non i686 targets built on i686 SliTaz: arm, x86_64.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]