Создание Pisi-пакетов

Making Pisi Packages

From PardusWiki

Jump to: navigation, search

This page is under construction.

You are welcome to assist in its construction by editing it as well.

This message should be deleted after editing.

Contents

[hide]

* 1 Basics

o 1.1 Packager's point of view

o 1.2 Packaging Mechanism

o 1.3 Pardus SVN Repository

o 1.4 File and Directory Locations

o 1.5 Structure of a PiSi Package

* 2 PiSi Package Building

o 2.1 pspec.xml

+ 2.1.1 Source part

+ 2.1.2 Package part

+ 2.1.3 History part

o 2.2 actions.py

+ 2.2.1 Actions API

* 3 Directories (comar and files)

o 3.1 comar directory

+ 3.1.1 package.py

+ 3.1.2 service.py

+ 3.1.3 Adding comar scripts to package

o 3.2 files directory

* 4 Other files

o 4.1 translations.xml

o 4.2 components.xml

* 5 Example

PİSİ (Packages Installed Successfully as Intended) is a binary package management system which have been developed within Pardus project. PİSİ has more function than just installing/uninstalling packages. For example, it is possible to regain old package setup automatically. Packages need to be processed as pisi packages and presented as binary packages for using them as pisi packages. For detailed information you can look at Pardus official site

Basics

Package: A program, document or any kind of data for installing to system

Source file: A file that includes files which belongs to package and generally presented as archive files and generally downloadable via internet. Programs generally uses files that are archived as .tar.gz files. Archived files need to include program's non-compiled source code, data that program needs and documents.

Compiling: Operation that needs to be done to make executable binary files of programs that is written in compilable programing language like C,C++.

Dependency: Other packages that program uses while it is running or compiling.