Software Packages: PuppyLinux

Software package suffixes denote the environment in which the package was compiled. This provides some indication of whether or not a certain package is compatible with one's operating system. One will not know of compatibility for sure unless the installation is actually attempted, so always have a back up of the current system before installing any package.

w (w5) - compiled within Wary

f - compiled within Fluppy

lucid (l, p5) - compiled within Lucid

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

Software Installation

Ensure that the latest available versions of the following pre-requisite packages are installed:
bzip2, curl, dosfstools, e2fsprogs, grep, ntfs3g, tar, wget, xz

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 save file to be at least 3 times the size of the package.

"How does one upgrade existing software?"
http://murga-linux.com/puppy/viewtopic.php?p=489219#489219

"To which location has the software package been downloaded to?"
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 the relevant PET software package which someone else has already kindly made, either from the official repository or from independent, user-contributed repositories (see below)

then single-left-click on it

Installing PETs into 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 PETs into full Puppy installations
No personal storage save files are involved. Download a PET software package; then single-left-click on it for automatic installation.

Un-installing PET packages
Go to: Menu > Setup > Puppy Package Manager
http://murga-linux.com/puppy/viewtopic.php?p=396935#396935

Installing and un-installing PET packages via the command-line interface

Installing TXZ software packages

download and install the software package file anywhere and outside any personal save file, such as /mnt/home (examples: opera, seamonkey, libreoffice

Installing SFS software packages

download and place the software package file at /mnt/home (examples: 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 > SFS-Load

Appendix

compiling How to Build (Compile) a Binary Package From the Source Code and Install It
SoftwarePackageCreation How to Create a Software Package for Puppy
DesktopIcons

PuppyLinux : software

Revision [16006]

Software Repositories

Software Installation

Appendix

Categories