Faik Uygur
0499786b1d
* created pisi.conf should have the values uncommented, these are the real values anyway. * package_cache default is set to False for package-manager for a new Pardus installation. This was the default behaviour for pm. But if a pisi.conf file exists (for an already installed system), setup.py does not overwrite it. So no package_cache_X values will be in pisi.conf. (Question: Why do we create pisi.conf in setup.py, why not an additional file) In this case package-manager's default is, use package cache to keep user's cached packages. - TODO: pisi should use these values in cli also, cause this is pisi.conf! or maybe this was not the right place for this from the start or was it? :/
PISI - Packages Installed Succesfully as Intended PISI is a new package manager for the PARDUS distribution. In Turkish PISI means "kitty", and like a kitty, it is featureful and small. Some of its distinctive features: - Implemented in python - Efficient and small - Package sources are written in XML and python - Uses LZMA for a better compression ratio - Fast database access implemented with berkeley DB - Integrates low-level and high-level package operations (dependency resolution) - Framework approach to build applications and tools upon - Comprehensive CLI and a user-friendly qt GUI (distributed separately) - Extremely simple package construction