Product SiteDocumentation Site

Chapter 4. Specifications

4.1. Architecture naming policy
4.1.1. What are architecture names?
4.1.2. Architecture names
4.2. Directory variables
4.2.1. What are directory variables?
4.2.2. List of Listaller directory variables
4.3. Dependency types
4.3.1. Rationale
4.3.2. Dependency description locations
4.3.3. Description file schema
4.3.4. Frameworks
4.4. Package settings file
4.4.1. What are package settings files?
4.5. IPK file listings
4.5.1. Rationale
4.5.2. Basic structure
4.5.3. Schema
4.6. IPK repository structure
4.6.1. What is an IPK package repository?
4.6.2. Directory overview
Listaller uses various file-formats and many specifications. Here you can find a description of them.
You can also learn about the idea of Listaller and the project plan.

4.1. Architecture naming policy

How Listaller treats architecture names

4.1.1. What are architecture names?

Architecture names are strings like "x86_64" or "i686" which define the system-architecture of the current computer.
Compiled programs can only run on the architecture they are built for. Therefore Listaller packages also need to be arch-specific. Unfortunately, there are quite a few architecture names around, e.g. for 64bit-PCs the vendor-neutral name "x86_64" or "amd64". For historical and compatibility reasons, Listaller uses the naming conventions described below.

4.1.2. Architecture names

Listaller uses the output string of the uname -m command for nearly all architectures, except for 32bit-PC and 64bit-PC architectures.
For AMD's 64bit architecture, with the name "x86_64" or "amd64", we use the vendor-name amd64. Listaller will only use and recognize this name.
For Intel's x86 architecture (names like "i386, "i486", "i686", ...) we use the name ix86. No other names are processed.
For any other architecture, no special name changes are applied and we use the name which is exposed by the Linux kernel.