here one instruction for building a pisi-package for example Opera Unite, which wrote me the kindly developer "Serdar":
First, make sure that you have system.devel component installed.
change to a root user by su -
then
write
pisi it -c system.devel
after this, install subversion
pisi it subversion.
subversion is needed to checkout the source codes.
so let's begin :)
first, checkout https://svn.pardus.org.tr/pardus/playground/sdalgic/network/web/opera-unite/
svn co https://svn.pardus.org.tr/pardus/playground/sdalgic/network/web/
here, you will see that kind of structure:
sdalgic@Virt-2009-Deus-Ex-Machina web $ ls -R
.:
component.xml opera-unite
./opera-unite:
actions.py files pspec.xml translations.xml
./opera-unite/files:
opera.desktop
************************************************
component.xml file at the upper directory of opera-unite package is essential to build the package.
Most of the packages are kept in that kind of repository structure. So keep in mind, in order to build a package with source repository, component.xml file in one level upper of the package directory is essential.
After you got the source package, investigate the files
there are
* actions.py : The instructions for building the package
* pspec.xml: Package specifications
* translations.xml : Package Summary and Description translations.
* files/ directory: Additional files, patches etc.
* comar/ directory: not present in this packages, but includes post-install scripts, pre-removal scripts etc..
For building a package, we use pisi build command. type pisi help bi for more information.
pisi bi -d pspec.xml
is the command you will write in the command line. -d option is for debugging purposes, it will be on by default in the next version of pisi ;)
After this, pisi package is being built. Just watch pisi build the package ;)
After the process has ended, you will see the package in your working directory. It will be opera-unite-10.00-1.pisi .
That's all. Pardus svn is here[1] . check out the repository and you can try building packages.
Take a look at pspec.xml file. It is easy to read, and you will get a clue about the package. The maintainer of the package, the source of the source package (Main source code of the program) The package's dependencies, the packages it conflicts, The file paths of the package.
btw, you can see the contents of the package by writing lspisi <package_name.pisi>
for ex:
sdalgic@Virt-2009-Deus-Ex-Machina opera-unite $ lspisi opera-unite-10.00-1.pisi
/usr/bin/opera
/usr/lib/opera/10.00/missingsyms.so
/usr/lib/opera/10.00/opera
/usr/lib/opera/10.00/operaplugincleaner
/usr/lib/opera/10.00/operapluginwrapper
/usr/lib/opera/10.00/spellcheck.so
/usr/lib/opera/10.00/works
/usr/lib/opera/plugins/libflashplayer.so
/usr/share/applications/opera.desktop
/usr/share/doc/opera/LGPL
/usr/share/doc/opera/LICENSE
/usr/share/icons/hicolor/16x16/apps/opera.png
These are the paths the contents of the package will go to.
Author