<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pacman - Xcraft</title>
    <link>/xcraft/pacman/index.html</link>
    <description>The Package Manager</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/xcraft/pacman/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Overview</title>
      <link>/xcraft/pacman/overview/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/xcraft/pacman/overview/index.html</guid>
      <description>TODO: some steps are not implemented…&#xA;The packages are created with wpkg as presented in the following diagram.&#xA;The definitions for all packages are in the packages/ directory.&#xA;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).</description>
    </item>
    <item>
      <title>Commands</title>
      <link>/xcraft/pacman/commands/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/xcraft/pacman/commands/index.html</guid>
      <description>Primary module that drives the wpkg command in order to make, build, install, remove, etc,… packages.&#xA;pacman.list List all packages available in the packages/ directory.&#xA;pacman.edit Create or edit a package [definition][2]. This function will start a wizard and generates a new directory in the packages/ directory. The [definition][2] is stored in a .yaml file.&#xA;pacman.make Generate a new package .deb accordingly to the [definitions][2]. This package is saved in a local [repository][3].</description>
    </item>
  </channel>
</rss>