/tags/toolchain/index.html Hugo en-us /xcraft/pacman/overview/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/pacman/overview/index.html TODO: some steps are not implemented… The packages are created with wpkg as presented in the following diagram. The definitions for all packages are in the packages/ directory. Step 1 All packages are described by a config.yaml file, see The package definitions page for details. Only the YAML file is mandatory. But for some packages, it can be necessary to have some resources directly in the package definition directory (only for core packages or very small packages). /xcraft/pacman/commands/pacman.list/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/pacman/commands/pacman.list/index.html /xcraft/pacman/commands/pacman.edit/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/pacman/commands/pacman.edit/index.html The package definitions The package definitions are located in the packages/ directory where you can find the sub-directories of the projects. Every project has a file named config.yaml. This file can be edited by hand or with the zog command. Tip It’s better to use zog or lokthar for editing unless you know exactly what are you going. Create or modify a package definition The command is just: zog create <the package name>. /xcraft/pacman/commands/pacman.make/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/pacman/commands/pacman.make/index.html It is possible to pass several packages or nothing. In the first case, all packages will be generated. If nothing is passed, then all packages are considered. pacman.make # To make all packages. pacman.make package1,package2 # To make only two packages. Sometimes it is interesting to make a package will all its dependencies. The following pattern @deps will do the trick. Of course, you can add other packages. pacman.make package1,@deps # To make package1 and its dependencies. /xcraft/pacman/commands/pacman.install/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/pacman/commands/pacman.install/index.html If the package is already installed, nothing happens. If the currently installed package is older, then this action will upgrade with the new version. Of course, all dependencies will be installed too. If a required dependency is not found in the repository, the installation will fail. MS Windows and MSI Maybe you have a package with an MSI installer. In this case, it can be possible that this MSI needs a reboot in order to continue the installation.