EN · EL · FR · ES · IT · RU · ZH · AR · HI · PT · DE
The Emblem
one thread, no dead ends
slacker's mark is a Cretan labyrinth with a labrys — the Minoan double axe — at its heart. The image is old, and it was chosen on purpose.
Ariadne's thread
In the myth, King Minos of Crete kept the Minotaur in a Labyrinth built beneath the palace of Knossos by the craftsman Daedalus — a structure so intricate that anyone who walked into it was lost. When Theseus came to face the Minotaur, it was Ariadne, daughter of Minos, who gave him the way out: a single ball of thread to unwind on the way in and follow back on the way out. (That thread — a clew — is the literal ancestor of the English word clue.)
The labyrinth of the myth is unicursal: not a maze of branching corridors and dead ends, but one long, winding path that leads inevitably to the centre and back out again. There is only one way through, and the thread is the proof of it.
The word labyrinthos itself belongs to Crete — to the labrys, the double-headed axe of Minoan Knossos, the "house of the double axe." So the axe sits at the centre of the emblem, where the thread arrives.
The same path, through dependencies
A dependency graph can feel like that Labyrinth: easy to get lost in, full of forks that lead nowhere. slacker's whole job is to be Ariadne's thread — to find the one correct path through it and hand it to you, plainly.
That principle runs all the way down:
- Dependencies come only from a package's own declared
.dep. slacker never guesses a fork. - Priority is absolute. The resolver never wanders off to a lower-priority source, and never quietly downgrades you.
- There are no dead ends. A
-currentupgrade that goes wrong can be walked back withrevert-pkg; whatever happens, there is a way back along the thread.
The same thread, in the development
The thread is not only the path slacker traces through your dependencies — it is also the path slacker itself is built along. The two meanings are one image.
slacker's version line never resets. Development is a single, unbroken thread:
0.x.x, always pre-release, always being drawn toward the next Slackware
-current — never starting over, never doubling back. A new line of work
continues the same 0.x thread rather than cutting it and beginning a fresh one;
the number only ever moves forward. The labyrinth is unicursal in the project's
own history too: one path, no dead ends, no going back to the start.
So the emblem says the same thing about the tool and about the work that makes it.
Follow the thread inward and it resolves your system; follow it the other way and
it is the line of every release, kept whole from the first 0.1 onward.
And the doubleness is not only in the reading — it is cut into the emblem itself. The labrys at the heart is a double axe: two blades on a single haft, meeting at the one point where the thread arrives. Two edges of one tool, the way the thread is two paths of one line — the path through your system, and the path of the project that builds it. The myth chose the symbol before slacker did; the two blades were always waiting for the two meanings.
A thread that draws itself
The emblem is not a stored picture. It is generated: the same kind of pathfinding the resolver performs is used to trace the single corridor of the labyrinth, and that traced thread is the logo. The mark draws itself the way slacker works — one path, found and followed.
slacker — one path through the dependency labyrinth. No dead ends.