Software Packages: PuppyLinux

Revision [27287]

This is an old revision of software made by coolpup on 2013-04-23 07:12:12.

cn::de::es::fr::gr::hu::it::ja::kr::nl::pl::pt::ru::se::us::vn::

HomePage > SoftwareIndex Software Index

Software Packages

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 to it

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 three main software package types, identified by their file extension:

.pet (intended for full and frugal Puppy installations; supersedes .pup which is now obsolete)

.sfs (intended for full, frugal or LiveDVD installations)

.txz (intended for full and frugal installations)

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:

fd64 - compiled within, and/or packaged for, Fatdog64

d64 - packaged from 64-bit Debian distribution binaries

d - packaged from 32-bit Debian distribution binaries

a - packaged from Arch distribution binaries

f - packaged from Fedora distribution binaries

s - packaged from Slackware distribution binaries

u - packaged from Ubuntu distribution binaries

up - compiled within a Woof-built Puppy with Ubuntu packages, e.g. PuppyPrecise

sp - compiled within a Woof-built Puppy with Slackware packages, e.g. Slacko

r - compiled within Racy

w (w5) - compiled within Wary

q (q1) - compiled within Quirky

p4 - compiled within Puppy 4

no suffix - packaged from software maintainer binaries

Pre-requisite packages

ensure that recent versions of the following packages are installed: +bzip2,+e2fsprogs,+grep,+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 TXZ software packages

acquire (download) the relevant TXZ software package file, e.g. qt, wine

then, after downloading has finished, single-left-click on it

then, choose one of the following options:

install into the existing filesystem

extract and place the software package directory anywhere (and outside any personal save file)

Installing PET software packages

acquire (download) the relevant pets PET software package file

then, after downloading has finished, single-left-click on it, e.g. ffmpeg, pidgin

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.