Revision [22907]
This is an old revision of software made by coolpup on 2012-08-02 10:50:52.
Software Packages
Official software packages are available via the ppm Puppy Package Manager:- using the start menu: Menu > Setup > Puppy Package Manager
- using the command-line interface:
ppm
There are two main software package types, identified by their file extension:
- .pet (intended for all full and frugal Puppy installations)
- .sfs (originally intended for frugal or LiveDVD installations)
Other software package types:
- .tar.xz or .txz (intended for all full and frugal Puppy installations)
- .pup (obsolete; superseded by .pet)
Pre-requisite packages
Ensure that recent versions of the following packages are installed: +bzip2,+curl,+dosfstools,+e2fsprogs,+grep,+ntfs3g,+tar,+wget,+xz
Partition space
Since the installation of any software package involves occupying partition space, the installation will fail if there is not sufficient, free space on the target installation partition. Sometimes installing PET and TXZ packages to frugal Puppy installations requires the amount of free space inside the personal storage file to be at least 3 times the size of the package.
Download location
One needs to know to which location a software package has been downloaded to. If a Web browser is used for downloading, then it would need to be manually configured to the user's preference.
Installing PET software packages
Acquire (download) the relevant pets PET software package then, after downloading has finished, single-left-click on it, e.g. pidgin, wine
To reverse the process, i.e. to un-install PET software packages, go to the uninstalling un-installing page.
Installing PET packages within frugal Puppy installations
- the software installation is only retained (or permanent) when it is installed after the creation of a personal storage save file. The software may be installed before the existence of a save file but the installation will be lost when shutting down or re-booting. A save file is created during the procedure of re-booting or shutting down for the very first time following a new, frugal Puppy installation.
- requires sufficient free space inside an already existing save file (the save file may need to be re-sized larger)
- after downloading a PET software package, single-left-click on it for automatic installation
Installing PET packages within full Puppy installations
No personal storage save files are involved. Download a PET software package; then single-left-click on it for automatic installation.
Installing TXZ software packages
Download the file, extract the contents, and place the software package directory anywhere (and outside any personal save file).
Installing SFS software packages
- download and place the software package at /mnt/home (e.g. JavaRuntimeEnvironment jre)
- then, either (A) follow the instructions at (requires re-booting): Menu > System > BootManager
- or, (B) follow the instructions at (does not require re-booting): Menu > Setup > SFSLoad SFS-Load
- for more information and how to install on full installation, see SquashFS
Software Repositories
[[SoftwareDisclaimer Software disclaimer: absolutely no warranty given or implied, so use any software package entirely at your own risk and always have multiple copies of the current operating system before installing any package onto it:
For example, http://distro.ibiblio.org/quirky/pet_packages-wary5/
More at PuppySites.
Software package names that contain a suffix denote the environment in which the package was compiling compiled (built). This provides some indication of whether or not a certain package is compatible with one's operating system, but one will not know of compatibility for sure unless the package is actually installed:
- r - compiled within Racy
- w (w5) - compiled within Wary
- pp - compiled within PuppyPrecise
- q (q1) - compiled within Quirky
- p4 - compiled within Puppy 4
- d - packaged from Debian distribution binaries
- s - packaged from Slackware distribution binaries
- u - packaged from Ubuntu distribution binaries
- no suffix - packaged from software maintainer binaries
