Revision history for software
Additions:
- When a package is installed via the puppy Package Manager, sometimes at the end of the installation the manager will check for required dependencies and let you know what is missing,
- Also, via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
- If none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
- Also, via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
- If none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
Deletions:
~~-
~~~When a package is installed via the puppy Package Manager, sometimes at the end of the installation the manager will check for required dependencies and let you know what is missing,
~~~Also, via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
~~-If none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
Additions:
Identifying missing dependencies:
Deletions:
Additions:
~~~When a package is installed via the puppy Package Manager, sometimes at the end of the installation the manager will check for required dependencies and let you know what is missing,
~~~Also, via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
~~-If none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
~~~Also, via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
~~-If none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
Deletions:
~~~ Also, via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
~~- If none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
Additions:
~Some packages are dependent on other packages being install, hence these are called dependencies. Sometimes a particular versions of a specific package is required. Even one .pet from one puppy version might have missing dependencies if used with another puppy version.
~~ When a package is installed via the puppy Package Manager, sometimes at the end of the installation the manager will check for required dependencies and let you know what is missing,
~~~ Also, via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
~~- If none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
~~ When a package is installed via the puppy Package Manager, sometimes at the end of the installation the manager will check for required dependencies and let you know what is missing,
~~~ Also, via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
~~- If none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
Deletions:
~~- When a package is installed via the puppy Package Manager, sometimes at the end of the installation the manager will check for required dependencies and let you know what is missing,
~~- also via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
~~- if none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
Revision [31972]
Edited on 2018-04-14 19:50:29 by PageStep007 [added identifying missing dependencies]Additions:
~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__.
~~ Some .rpm and .deb packages will install, but often they are built for other linux operating systems and assume that the system has all files it needs, but which may not be on your system. Sometimes installing the missing files will get a program going.
~Some packages are dependent on other packages being install, hence these are called dependencies. Sometimes a particular versions of a specific package is required.Even one .pet from one puppy version might have missing dependencies if used with another puppy version.
~~-
~~-
~-Identifying missing dependencies:
~~- When a package is installed via the puppy Package Manager, sometimes at the end of the installation the manager will check for required dependencies and let you know what is missing,
~~- also via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
~~- if none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
~~ Some .rpm and .deb packages will install, but often they are built for other linux operating systems and assume that the system has all files it needs, but which may not be on your system. Sometimes installing the missing files will get a program going.
~Some packages are dependent on other packages being install, hence these are called dependencies. Sometimes a particular versions of a specific package is required.Even one .pet from one puppy version might have missing dependencies if used with another puppy version.
~~-
~~-
~-Identifying missing dependencies:
~~- When a package is installed via the puppy Package Manager, sometimes at the end of the installation the manager will check for required dependencies and let you know what is missing,
~~- also via Menu>setup>check dependencies installed pkg, you can choose from a list, any program you have tried to install and clicking the check dependencies button will check for what is missing.
~~- if none of these are successful a more involved way is to use menu>filesystem>pfind file finder, to do a search through your computer to find the executable file that initiates the program. Navigate to that directory and open a terminal. (right click in the directory and select window>terminal here, to get a terminal, relative to that directory) then type ./ and the name of the executable file. If all goes well the program will try to start, and results of each step will show in the terminal. When it gets to a missing dependency it will stop and let you know what it could not find, eg: libxyz.so.0 . There may also be a path to where it should be, or some information which may help you do an internet search for the missing file. It may be in a .rpm or .deb from other linux system repositories, or it may be part of another package. Install it. Then ./ and the program executable again. If it was successful it will run the installation and pass onto other steps. If it comes up again, that was not the right file or it got installed in the wrong place. Uninstall it so as to not clog your system with junk. Use the puppy package manager uninstall button to locate and uninstall it. Then try again. some programs have few missing dependencies, and other a lot. Perseverance is the key. One happy moment will hopefully occur, when you have all of them installed the program will open and run. (go celebrate)
Deletions:
~Some packages are dependent on other packages being install, hence these are called dependencies. Sometimes a particular versions of a specific package is required.
Additions:
~Software packages allow the easy installation of applications (AKA apps, programs etc.). Examples of applications include an accounts package or a CAD program.
Deletions:
Additions:
~Software is the instructions or code that runs the operating system (Puppy Linux) and applications (AKA application programs or apps). Examples of application programs would include an accounts package or a CAD program.
~Puppy Linux like most versions of Linux come with a lot of built in programs. The easiest way to add more is either a self installing file such as a [[PET]], or by using a package manger such as [[PPM]].
==Precautions==
~Most software comes with a [[SoftwareDisclaimer disclaimer]], usually stating something along the lines of:
~~Absolutely no warranty given or implied, so use any software package entirely at your own risk.
~system [[backup]]: **//always have multiple copies of your 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%%
~un-official software packages are available from repositories such as: [[http://murga-linux.com/puppy/index.php?f=63 murga-linux.com]]
~there are three main software package types, identified by their file extension:
~~**//.txz//** (intended for full and frugal installations)
~~**//.pet//** (intended for full and [[installationfrugal frugal installations]]; supersedes //.pup// which is now obsolete)
~~**//.sfs//** (intended for frugal or LiveDVD 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__
==Prerequisite packages==
~Some packages are dependent on other packages being install, hence these are called dependencies. Sometimes a particular versions of a specific package is required.
~Common dependencies:
~~ +[[bzip2]],+[[e2fsprogs]],+[[grep]],+[[tar]],+[[wget]],+[[xz]]
~Puppy Linux like most versions of Linux come with a lot of built in programs. The easiest way to add more is either a self installing file such as a [[PET]], or by using a package manger such as [[PPM]].
==Precautions==
~Most software comes with a [[SoftwareDisclaimer disclaimer]], usually stating something along the lines of:
~~Absolutely no warranty given or implied, so use any software package entirely at your own risk.
~system [[backup]]: **//always have multiple copies of your 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%%
~un-official software packages are available from repositories such as: [[http://murga-linux.com/puppy/index.php?f=63 murga-linux.com]]
~there are three main software package types, identified by their file extension:
~~**//.txz//** (intended for full and frugal installations)
~~**//.pet//** (intended for full and [[installationfrugal frugal installations]]; supersedes //.pup// which is now obsolete)
~~**//.sfs//** (intended for frugal or LiveDVD 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__
==Prerequisite packages==
~Some packages are dependent on other packages being install, hence these are called dependencies. Sometimes a particular versions of a specific package is required.
~Common dependencies:
~~ +[[bzip2]],+[[e2fsprogs]],+[[grep]],+[[tar]],+[[wget]],+[[xz]]
Deletions:
~-system [[backup]]: **//always have multiple copies of your 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%%
~-un-official software packages are available from repositories such as: [[http://murga-linux.com/puppy/index.php?f=63 murga-linux.com]]
~-there are three main software package types, identified by their file extension:
~~-**//.txz//** (intended for full and frugal installations)
~~-**//.pet//** (intended for full and [[installationfrugal frugal installations]]; supersedes //.pup// which is now obsolete)
~~-**//.sfs//** (intended for frugal or LiveDVD 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__
==Pre-requisite packages==
~Sometimes an updated version following packages are required: +[[bzip2]],+[[e2fsprogs]],+[[grep]],+[[tar]],+[[wget]],+[[xz]]
Additions:
~-un-official software packages are available from repositories such as: [[http://murga-linux.com/puppy/index.php?f=63 murga-linux.com]]
~-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__
~-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__
Deletions:
~-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__:
~~-//up// - compiled & packaged for i686 processors, within 32-bit [[upup]] a [[Woof]]-built Puppy using Ubuntu packages, e.g. PuppyPrecise
~~-//sp// - compiled & packaged within 32-bit [[spup]], a [[Woof]]-built Puppy using Slackware packages, e.g. [[Slacko]]
~~-//fd64// - compiled & packaged for i686 processors, within 64-bit [[Fatdog64]]
~ - //d// - packaged from 32-bit Debian distribution binaries
~ - //s// - packaged from Slackware distribution binaries
~ - //u// - packaged from Ubuntu distribution binaries
~ - //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
Additions:
{{include tonguesSoftware}}
[[HomePage]] > [[SoftwareIndex Software Index]]
[[HomePage]] > [[SoftwareIndex Software Index]]
Deletions:
Additions:
~Sometimes an updated version following packages are required: +[[bzip2]],+[[e2fsprogs]],+[[grep]],+[[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 [[SaveFile|personal storage file]]// to be at least 3 times the size of the package
~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 [[SaveFile|personal storage file]]// to be at least 3 times the size of the package
Deletions:
~-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
Additions:
====Software Packages====
~[[Software Repositories|]]
~[[SoftwareDisclaimer Software disclaimer]]
~[[SFS]]
~[[PET]]
~[[TXZ]]
~[[Software Repositories|]]
~[[SoftwareDisclaimer Software disclaimer]]
~[[SFS]]
~[[PET]]
~[[TXZ]]
Deletions:
==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 to it//**:
~ - http://distro.ibiblio.org/quirky/
~ - http://distro.ibiblio.org/puppylinux/
~ - http://www.smokey01.com/devs/
~ - http://182.164.208.211/puppy/opt/
~ - http://shino.pos.to/linux/downloads.html
~ - http://shino.pos.to/linux/puppy/
~ - http://ppm.scottjarvis.com
~ - http://www.murga-linux.com/puppy/index.php?f=63
~ - [[PuppySites more]]
Deletions:
Additions:
~~-//up// - compiled & packaged for i686 processors, within 32-bit [[upup]] a [[Woof]]-built Puppy using Ubuntu packages, e.g. PuppyPrecise
~~-//sp// - compiled & packaged within 32-bit [[spup]], a [[Woof]]-built Puppy using Slackware packages, e.g. [[Slacko]]
~~-//sp// - compiled & packaged within 32-bit [[spup]], a [[Woof]]-built Puppy using Slackware packages, e.g. [[Slacko]]
Deletions:
~~-//sp// - compiled within 32-bit [[spup]], a [[Woof]]-built Puppy using Slackware packages, e.g. [[Slacko]]
Additions:
~~-//up// - compiled & packaged for i686 processors, within 32-bit [[upup Ubuntu Puppy]] a [[Woof]]-built Puppy using Ubuntu packages, e.g. PuppyPrecise
~~-//sp// - compiled within 32-bit [[spup]], a [[Woof]]-built Puppy using Slackware packages, e.g. [[Slacko]]
~~-//fd64// - compiled & packaged for i686 processors, within 64-bit [[Fatdog64]]
~ - //d// - packaged from 32-bit Debian distribution binaries
~~-//sp// - compiled within 32-bit [[spup]], a [[Woof]]-built Puppy using Slackware packages, e.g. [[Slacko]]
~~-//fd64// - compiled & packaged for i686 processors, within 64-bit [[Fatdog64]]
~ - //d// - packaged from 32-bit Debian distribution binaries
Deletions:
~ - //d// - packaged from 32-bit Debian distribution i486 binaries
~~-//fd64// - compiled within, and/or packaged for, 64-bit [[Fatdog64]]
~ - //sp// - compiled within a [[Woof]]-built Puppy with Slackware packages, e.g. [[Slacko]]
Additions:
====**Software Packages**====
~-system [[backup]]: **//always have multiple copies of your current operating system __before__ installing any package to it//**
~ - //up// - compiled for i686 processors, within 32-bit [[upup Ubuntu Puppy]], e.g. PuppyPrecise
~ - //d// - packaged from 32-bit Debian distribution i486 binaries
~~-//fd64// - compiled within, and/or packaged for, 64-bit [[Fatdog64]]
~-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
~-system [[backup]]: **//always have multiple copies of your current operating system __before__ installing any package to it//**
~ - //up// - compiled for i686 processors, within 32-bit [[upup Ubuntu Puppy]], e.g. PuppyPrecise
~ - //d// - packaged from 32-bit Debian distribution i486 binaries
~~-//fd64// - compiled within, and/or packaged for, 64-bit [[Fatdog64]]
~-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
Deletions:
~-system backup: **//always have multiple copies of your current operating system __before__ installing any package to it//**
~~-//fd64// - compiled within, and/or packaged for, [[Fatdog64]]
~ - //d// - packaged from 32-bit Debian distribution binaries
~ - //f// - packaged from Fedora distribution binaries
~ - //up// - compiled within a [[Woof]]-built Puppy with Ubuntu packages, e.g. PuppyPrecise
~-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.
Additions:
~-[[SoftwareDisclaimer software disclaimer]]: **absolutely no warranty given or implied, so use any software package entirely at your own risk**
Deletions:
Additions:
~-system backup: **//always have multiple copies of your current operating system __before__ installing any package to it//**
Deletions:
Deletions:
~[[SFS]]
~[[PET]]
Additions:
[[SoftwareDisclaimer software disclaimer]]: **absolutely no warranty given or implied, so use any software package entirely at your own risk**
~-**//always have multiple copies of your current operating system __before__ installing any package to it//**
~-**//always have multiple copies of your current operating system __before__ installing any package to it//**
Deletions:
~-**//always have multiple copies of the current operating system __before__ installing any package to it//**
Additions:
~[[SoftwareDisclaimer software disclaimer]]: **absolutely no warranty given or implied, so use any software package entirely at your own risk**
Deletions:
Additions:
~[[SoftwareDisclaimer software disclaimer]]: **absolutely no warranty given or implied, so use any software package entirely at your own risk
~-**//always have multiple copies of the current operating system __before__ installing any package to it//**
~-**//always have multiple copies of the current operating system __before__ installing any package to it//**
Deletions:
Additions:
{{include tonguesSoftware}}[[HomePage]] > [[SoftwareIndex Software Index]]
~-un-official software packages are available from repositories such as: [[http://www.smokey01.com/coolpup smokey01.com]] | [[http://murga-linux.com/puppy/index.php?f=63 murga-linux.com]]
~~-**//.sfs//** (intended for frugal or LiveDVD installations)
~-un-official software packages are available from repositories such as: [[http://www.smokey01.com/coolpup smokey01.com]] | [[http://murga-linux.com/puppy/index.php?f=63 murga-linux.com]]
~~-**//.sfs//** (intended for frugal or LiveDVD installations)
Deletions:
[[HomePage]] > [[SoftwareIndex Software Index]]
~~-**//.sfs//** (intended for full, frugal or LiveDVD installations)
~~-//d64// - packaged from 64-bit Debian distribution binaries
Additions:
~~-**//.pet//** (intended for full and [[installationfrugal frugal installations]]; supersedes //.pup// which is now obsolete)
Deletions:
Additions:
~-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__:
Deletions:
Additions:
~~-**//.pet//** (intended for full and frugal Puppy installations; supersedes //.pup// which is now obsolete)
~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__:
~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__:
Deletions:
~-other software package types:
~~-//.pup// software package type is obsolete and superseded by //.pet//
~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__:
~[[TXZ]]
Additions:
~ - //d// - packaged from 32-bit Debian distribution binaries
Deletions:
Additions:
~~-//fd64// - compiled within, and/or packaged for, [[Fatdog64]]
~~-//d64// - packaged from 64-bit Debian distribution binaries
~~-//d64// - packaged from 64-bit Debian distribution binaries
Deletions:
~-//d64// - packaged from 64-bit Debian distribution binaries
Additions:
~-ensure that recent versions of the following packages are installed: ##+[[bzip2]],+[[e2fsprogs]],+[[grep]],+[[tar]],+[[wget]],+[[xz]]##
~-//fd64// - compiled within, and/or packaged for, [[Fatdog64]]
~-//d64// - packaged from 64-bit Debian distribution binaries
~-//fd64// - compiled within, and/or packaged for, [[Fatdog64]]
~-//d64// - packaged from 64-bit Debian distribution binaries
Deletions:
Additions:
{{include tonguesSoftware}}
~[[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//**
~~-**//.pet//** (intended for full and frugal Puppy installations)
~~-**//.sfs//** (intended for full, frugal or LiveDVD installations)
==Installing TXZ software packages==
~-acquire (download) the relevant [[TXZ]] software package file, e.g. [[qt]], [[wine]]
==Installing PET software packages==
==Installing SFS software packages==
~-download and place the [[squashfs SFS]] software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], then
~[[JWMMenuCategory How to add and remove 'Puppy menu' items]]
~[[SoftwareDisclaimer Software disclaimer]]
~[[SFS]]
~[[PET]]
~[[TXZ]]
CategoryComponent
~[[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//**
~~-**//.pet//** (intended for full and frugal Puppy installations)
~~-**//.sfs//** (intended for full, frugal or LiveDVD installations)
==Installing TXZ software packages==
~-acquire (download) the relevant [[TXZ]] software package file, e.g. [[qt]], [[wine]]
==Installing PET software packages==
==Installing SFS software packages==
~-download and place the [[squashfs SFS]] software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], then
~[[JWMMenuCategory How to add and remove 'Puppy menu' items]]
~[[SoftwareDisclaimer Software disclaimer]]
~[[SFS]]
~[[PET]]
~[[TXZ]]
CategoryComponent
Deletions:
~~-**//.pet//** (intended for all full and frugal Puppy installations)
~~-**//.sfs//** (intended for frugal or LiveDVD installations)
==**Installing TXZ software packages**==
~-acquire (download) the relevant TXZ software package file, e.g. [[qt]], [[wine]]
==**Installing PET software packages**==
==**Installing [[squashfs SFS]] software packages**==
~-download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], then
Additions:
~-then, after downloading has finished, single-left-click on it
~-then, choose one of the following options:
~-then, choose one of the following options:
Deletions:
Additions:
~~-**//.txz//** (intended for full and frugal installations)
Deletions:
Deletions:
Additions:
~-acquire (download) the relevant TXZ software package file, e.g. [[qt]], [[wine]]
~-then, after downloading has finished, single-left-click on it which will offer two options:
~-acquire (download) the relevant [[pets PET]] software package file
~-then, after downloading has finished, single-left-click on it, e.g. [[ffmpeg]], [[pidgin]]
~-then, after downloading has finished, single-left-click on it which will offer two options:
~-acquire (download) the relevant [[pets PET]] software package file
~-then, after downloading has finished, single-left-click on it, e.g. [[ffmpeg]], [[pidgin]]
Deletions:
~-clicking on the file will offer two options:
~-acquire (download) the relevant [[pets PET]] software package
~-then, after downloading has finished, single-left-click on it, e.g. [[ffmpeg]], [[pidgin]], [[qt]], [[wine]]
Additions:
~~-**//.tar.xz//** or **//.txz//** (intended for full and frugal installations)
Deletions:
Additions:
~-there are three main software package types, identified by their file extension:
~~-//.pup// software package type is obsolete and superseded by //.pet//
~~-//.pup// software package type is obsolete and superseded by //.pet//
Deletions:
~~-//.pup// (obsolete; superseded by //.pet//)
Additions:
~-download the file
~-clicking on the file will offer two options:
~~-install into the existing filesystem
~~-extract and place the software package directory anywhere (and outside any personal save file)
~ - //a// - packaged from Arch distribution binaries
~ - //f// - packaged from Fedora distribution binaries
~-clicking on the file will offer two options:
~~-install into the existing filesystem
~~-extract and place the software package directory anywhere (and outside any personal save file)
~ - //a// - packaged from Arch distribution binaries
~ - //f// - packaged from Fedora distribution binaries
Deletions:
Additions:
~-then, after downloading has finished, single-left-click on it, e.g. [[ffmpeg]], [[pidgin]], [[qt]], [[wine]]
~-download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], then
~-download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], then
Deletions:
~-download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], [[qt]]), then
Additions:
~-download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], [[qt]]), then
Deletions:
Additions:
~-download the file, extract the contents, and place the software package directory anywhere (and outside any personal save file).
Deletions:
Additions:
~~-using the start menu: //Menu > Setup > Puppy Package Manager//
~~-using the command-line interface:%%ppm%%
~~-**//.pet//** (intended for all full and frugal Puppy installations)
~~-**//.sfs//** (intended for frugal or LiveDVD installations)
~~-**//.tar.xz//** or **//.txz//** (intended for all full and frugal Puppy installations)
~~-//.pup// (obsolete; superseded by //.pet//)
~-ensure that recent versions of the following packages are installed: +[[bzip2]],+[[curl]],+[[dosfstools]],+[[e2fsprogs]],+[[grep]],+[[ntfs3g]],+[[tar]],+[[wget]],+[[xz]]
~~-using the command-line interface:%%ppm%%
~~-**//.pet//** (intended for all full and frugal Puppy installations)
~~-**//.sfs//** (intended for frugal or LiveDVD installations)
~~-**//.tar.xz//** or **//.txz//** (intended for all full and frugal Puppy installations)
~~-//.pup// (obsolete; superseded by //.pet//)
~-ensure that recent versions of the following packages are installed: +[[bzip2]],+[[curl]],+[[dosfstools]],+[[e2fsprogs]],+[[grep]],+[[ntfs3g]],+[[tar]],+[[wget]],+[[xz]]
Deletions:
- using the command-line interface:%%ppm%%
- **//.pet//** (intended for all full and frugal Puppy installations)
- **//.sfs//** (intended for frugal or LiveDVD installations)
- **//.tar.xz//** or **//.txz//** (intended for all full and frugal Puppy installations)
- //.pup// (obsolete; superseded by //.pet//)
~-Ensure that recent versions of the following packages are installed: +[[bzip2]],+[[curl]],+[[dosfstools]],+[[e2fsprogs]],+[[grep]],+[[ntfs3g]],+[[tar]],+[[wget]],+[[xz]]
Additions:
~-official software packages are available via the [[ppm Puppy Package Manager]]:
~-there are two main software package types, identified by their file extension:
~-other software package types:
~-Ensure that recent versions of the following 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 storage file// to be at least 3 times the size of the package.
~-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
~-acquire (download) the relevant [[pets PET]] software package
~-then, after downloading has finished, single-left-click on it, e.g. [[pidgin]], [[wine]], [[ffmpeg]]
~-to reverse the process, i.e. to un-install PET software packages, go to the [[uninstalling un-installing]] page.
~-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
~-no personal storage save files are involved
~-download a PET software package; then single-left-click on it for automatic installation.
==**Installing [[squashfs SFS]] software packages**==
~-download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], [[qt]], [[wine]]), 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]]//
~-there are two main software package types, identified by their file extension:
~-other software package types:
~-Ensure that recent versions of the following 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 storage file// to be at least 3 times the size of the package.
~-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
~-acquire (download) the relevant [[pets PET]] software package
~-then, after downloading has finished, single-left-click on it, e.g. [[pidgin]], [[wine]], [[ffmpeg]]
~-to reverse the process, i.e. to un-install PET software packages, go to the [[uninstalling un-installing]] page.
~-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
~-no personal storage save files are involved
~-download a PET software package; then single-left-click on it for automatic installation.
==**Installing [[squashfs SFS]] software packages**==
~-download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], [[qt]], [[wine]]), 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]]//
Deletions:
There are two main software package types, identified by their file extension:
Other software package types:
~Ensure that recent versions of the following 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 storage file// to be at least 3 times the size of the package.
~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.
~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.
~ - 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
~No personal storage save files are involved. Download a PET software package; then single-left-click on it for automatic installation.
==**Installing SFS software packages**==
- download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], [[qt]], [[wine]])
- 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]]
Additions:
~ - [[PuppySites more]]
Deletions:
Additions:
[[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//**
~-[[PuppySites more]]
~-[[PuppySites more]]
Deletions:
~[[PuppySites more]]
Additions:
~~-http://distro.ibiblio.org/quirky/pet_packages-wary5/
~[[PuppySites more]]
~[[PuppySites more]]
Deletions:
~ More at PuppySites.
Additions:
~[[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//**
---
~[[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//**:
---
---
~[[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//**:
---
Deletions:
Additions:
~ - //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]]
~ - //sp// - compiled within a [[Woof]]-built Puppy with Slackware packages, e.g. [[Slacko]]
Deletions:
~ - //spup// - compiled within a [[Woof]]-built Puppy with Slackware packages, e.g. [[Slacko]]
Additions:
~ - //upup// - compiled within a [[Woof]]-built Puppy with Ubuntu packages, e.g. PuppyPrecise
~ - //spup// - compiled within a [[Woof]]-built Puppy with Slackware packages, e.g. [[Slacko]]
~ - //spup// - compiled within a [[Woof]]-built Puppy with Slackware packages, e.g. [[Slacko]]
Deletions:
Additions:
~ - //up// - compiled within a [[Woof]]-built Puppy with Ubuntu packages, e.g. PuppyPrecise
Deletions:
No Differences
Additions:
~ - //up// - compiled within PuppyPrecise
Deletions:
Additions:
~[[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//**:
Deletions:
Additions:
- download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]], [[libreoffice]], [[qt]], [[wine]])
Deletions:
Additions:
- **//.sfs//** (intended for frugal or LiveDVD installations)
Deletions:
Additions:
~Download the file, extract the contents, and place the software package directory anywhere (and outside any personal save file).
- download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]])
- download and place the software package at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]])
Deletions:
- download and place the software package file at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]])
Additions:
~Ensure that recent versions of the following packages are installed: +[[bzip2]],+[[curl]],+[[dosfstools]],+[[e2fsprogs]],+[[grep]],+[[ntfs3g]],+[[tar]],+[[wget]],+[[xz]]
~Download and install the software package file anywhere, and outside any personal save file.
~Download and install the software package file anywhere, and outside any personal save file.
Deletions:
~Download and install the software package file anywhere, and outside any personal save file, e.g. [[libreoffice]], [[opera]], [[seamonkey]], [[thunderbird]]
Additions:
~[[compiling How to build (compile) a software package from source code]]
Deletions:
~[[SquashFS SFS]]
Additions:
~[[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//**:
~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__:
~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__:
Deletions:
~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__.
~[[SoftwareDisclaimer]]
Additions:
~Software disclaimer: **absolutely no warranty given or implied, so use any software package entirely at your own risk and //always have a back up of the current system __before__ installing any package//**.
~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]]
~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]]
Deletions:
~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. 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//.
Additions:
- for more information and how to install on full installation, see [[SquashFS]]
Deletions:
Additions:
~Acquire (download) the relevant [[pets PET]] software package then, after downloading has finished, single-left-click on it, e.g. [[pidgin]], [[wine]]
Deletions:
Additions:
- **//.sfs//** (originally intended for frugal or LiveDVD installations)
~Acquire (download) the relevant [[PET pets]] software package then, after downloading has finished, single-left-click on it, e.g. [[pidgin]], [[wine]]
- for more information and how to install on full installation, see [[SquashSFS]]
==Also on the wiki==
~[[SquashFS SFS]]
~Acquire (download) the relevant [[PET pets]] software package then, after downloading has finished, single-left-click on it, e.g. [[pidgin]], [[wine]]
- for more information and how to install on full installation, see [[SquashSFS]]
==Also on the wiki==
~[[SquashFS SFS]]
Deletions:
~Acquire (download) the relevant PET software package then, after downloading has finished, single-left-click on it, e.g. [[pidgin]], [[wine]]
==Also see==
Additions:
==**Installing PET software packages**==
Deletions:
==Installing PET software packages==
Additions:
~ - http://182.164.208.211/puppy/opt/
Additions:
~ More at PuppySites.
Deletions:
~ - more on PuppySites page.
Additions:
~ For example, http://distro.ibiblio.org/quirky/pet_packages-wary5/
~Others:
~Others:
Additions:
====Software Packages====
Additions:
~ - //pp// - compiled within PuppyPrecise
Additions:
- using the start menu: //Menu > Setup > Puppy Package Manager//
- using the command-line interface:%%ppm%%
- **//.pet//** (intended for all full and frugal Puppy installations)
- **//.sfs//** (intended for all frugal or LiveDVD installations)
- **//.tar.xz//** or **//.txz//** (intended for all full and frugal Puppy installations)
- //.pup// (obsolete; superseded by //.pet//)
- using the command-line interface:%%ppm%%
- **//.pet//** (intended for all full and frugal Puppy installations)
- **//.sfs//** (intended for all frugal or LiveDVD installations)
- **//.tar.xz//** or **//.txz//** (intended for all full and frugal Puppy installations)
- //.pup// (obsolete; superseded by //.pet//)
Deletions:
~ - using the command-line interface:%%ppm%%
~ - **//.pet//** (intended for all full and frugal Puppy installations)
~ - **//.sfs//** (intended for all frugal or LiveDVD installations)
~ - **//.tar.xz//** or **//.txz//** (intended for all full and frugal Puppy installations)
~ - //.pup// (obsolete; superseded by //.pet//)
Additions:
Official software packages are available via the [[ppm Puppy Package Manager]]:
There are two main software package types, identified by their file extension:
Other software package types:
There are two main software package types, identified by their file extension:
Other software package types:
Deletions:
~Official software packages are available via the [[ppm Puppy Package Manager]]:
~There are two main software package types, identified by their file extension:
~Other software package types:
Additions:
~Acquire (download) the relevant 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.
- or, (B) follow the instructions at (does not require re-booting): //Menu > Setup > [[SFSLoad SFS-Load]]//
~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.
- or, (B) follow the instructions at (does not require re-booting): //Menu > Setup > [[SFSLoad SFS-Load]]//
Deletions:
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.
- or, (B) follow the instructions at (does not require re-booting): //Menu > Setup > [[http://www.murga-linux.com/puppy/viewtopic.php?t=64354 SFS-Load]]//
Additions:
~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//** (intended for all 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//)
====Software installation====
~Ensure that the latest available versions of the following 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 storage file// to be at least 3 times the size of the package.
~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==
==**Installing TXZ software packages**==
~Download and install the software package file anywhere, and outside any personal save file, e.g. [[libreoffice]], [[opera]], [[seamonkey]], [[thunderbird]]
==**Installing SFS software packages**==
==Software Repositories==
~Software disclaimer: absolutely no warranty given or implied, so use any software package entirely at your own risk
~ - http://distro.ibiblio.org/puppylinux/
~ - http://distro.ibiblio.org/quirky/
~ - http://www.smokey01.com/devs/
~ - http://shino.pos.to/linux/downloads.html
~ - http://shino.pos.to/linux/puppy/
~ - http://ppm.scottjarvis.com
~ - http://www.murga-linux.com/puppy/index.php?f=63
~ - more on PuppySites page.
~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. 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]]
~ - //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
~[[compiling How to build (compile) a software package from the source code and install it]]
~[[SoftwarePackageCreation How to create a software package for Puppy]]
~[[DesktopIcons How to create desktop icons]]
~[[SoftwareDisclaimer]]
~ - 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//** (intended for all 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//)
====Software installation====
~Ensure that the latest available versions of the following 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 storage file// to be at least 3 times the size of the package.
~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==
==**Installing TXZ software packages**==
~Download and install the software package file anywhere, and outside any personal save file, e.g. [[libreoffice]], [[opera]], [[seamonkey]], [[thunderbird]]
==**Installing SFS software packages**==
==Software Repositories==
~Software disclaimer: absolutely no warranty given or implied, so use any software package entirely at your own risk
~ - http://distro.ibiblio.org/puppylinux/
~ - http://distro.ibiblio.org/quirky/
~ - http://www.smokey01.com/devs/
~ - http://shino.pos.to/linux/downloads.html
~ - http://shino.pos.to/linux/puppy/
~ - http://ppm.scottjarvis.com
~ - http://www.murga-linux.com/puppy/index.php?f=63
~ - more on PuppySites page.
~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. 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]]
~ - //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
~[[compiling How to build (compile) a software package from the source code and install it]]
~[[SoftwarePackageCreation How to create a software package for Puppy]]
~[[DesktopIcons How to create desktop icons]]
~[[SoftwareDisclaimer]]
Deletions:
- 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//** (intended for all 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//)
===Software installation===
Ensure that the latest available versions of the following 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 storage file// to be at least 3 times the size of the package.
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**===
===**Installing TXZ software packages**===
Download and install the software package file anywhere, and outside any personal save file, e.g. [[libreoffice]], [[opera]], [[seamonkey]], [[thunderbird]]
===**Installing [[http://puppylinux.org/wikka/Squashfs SFS]] software packages**===
==={{color text="Software Repositories" c="green"}}===
Software disclaimer: absolutely no warranty given or implied, so use any software package entirely at your own risk
- http://distro.ibiblio.org/puppylinux/
- http://distro.ibiblio.org/quirky/
- http://www.smokey01.com/devs/
- http://shino.pos.to/linux/downloads.html
- http://shino.pos.to/linux/puppy/
- http://ppm.scottjarvis.com
- http://www.murga-linux.com/puppy/index.php?f=63
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. 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]]
- //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
[[compiling How to build (compile) a software package from the source code and install it]]
[[SoftwarePackageCreation How to create a software package for Puppy]]
[[DesktopIcons How to create desktop icons]]
[[SoftwareDisclaimer]]
Additions:
====About Software in Puppy====
Additions:
- no suffix - packaged from software maintainer binaries
Deletions:
- //lucid// (//l//, //p5//) - compiled within Lucid
- no suffix - packaged from software maintainer binaries
Additions:
- http://ppm.scottjarvis.com
- http://www.murga-linux.com/puppy/index.php?f=63
- http://www.murga-linux.com/puppy/index.php?f=63
Deletions:
- http://puppeee.com/files/
- http://ppm.scottjarvis.com/
- [[SoftwareIndex Wiki Software Index]]
Additions:
Official software packages are available via the [[ppm Puppy Package Manager]]:
- using the start menu: //Menu > Setup > Puppy Package Manager//
- using the start menu: //Menu > Setup > Puppy Package Manager//
Deletions:
- using the start menu: //Menu > Setup > [[PPM Puppy Package Manager]]//
Additions:
- using the start menu: //Menu > Setup > [[PPM Puppy Package Manager]]//
- using the command-line interface:%%ppm%%
- using the command-line interface:%%ppm%%
Deletions:
- Using the command-line interface:%%ppm%%
Additions:
- Using the command-line interface:%%ppm%%
Deletions:
Additions:
- Using the start menu: //Menu > Setup > [[PPM Puppy Package Manager]]//
- Using the command-line interace: %%ppm%%
- Using the command-line interace: %%ppm%%
Deletions:
Additions:
Ensure that the latest available versions of the following packages are installed: [[bzip2]], [[curl]], [[dosfstools]], [[e2fsprogs]], [[grep]], [[ntfs3g]], [[tar]], [[wget]], [[xz]]
Deletions:
[[bzip2]], [[curl]], [[dosfstools]], [[e2fsprogs]], [[grep]], [[ntfs3g]], [[tar]], [[wget]], [[xz]]
Additions:
- download and place the software package file at **///mnt/home//** (e.g. [[JavaRuntimeEnvironment jre]])
Deletions:
Additions:
==Pre-requisite packages==
==Partition space==
==Download location==
===**Installing PET software packages**===
===**Installing TXZ software packages**===
===**Installing [[http://puppylinux.org/wikka/Squashfs SFS]] software packages**===
==Partition space==
==Download location==
===**Installing PET software packages**===
===**Installing TXZ software packages**===
===**Installing [[http://puppylinux.org/wikka/Squashfs SFS]] software packages**===
Deletions:
**Installing PET software packages**
**Installing TXZ software packages**
**Installing [[http://puppylinux.org/wikka/Squashfs SFS]] software packages**
Deletions:
Deletions:
[[Pets Pet files]]
[[SquashFS SFS files]]
Additions:
Acquire (download) the relevant PET software package then, after downloading has finished, single-left-click on it, e.g. [[pidgin]], [[wine]]
Deletions:
Additions:
Acquire (download) the relevant PET software package then 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.
Download and install the software package file anywhere, and outside any personal save file, e.g. [[libreoffice]], [[opera]], [[seamonkey]], [[thunderbird]]
To reverse the process, i.e. to un-install PET software packages, go to the [[uninstalling un-installing]] page.
Download and install the software package file anywhere, and outside any personal save file, e.g. [[libreoffice]], [[opera]], [[seamonkey]], [[thunderbird]]
Deletions:
Download and install the software package file anywhere, and outside any personal save file, e.g. [[opera]], [[seamonkey]], [[thunderbird]], [[libreoffice]]
Additions:
Download and install the software package file anywhere, and outside any personal save file, e.g. [[opera]], [[seamonkey]], [[thunderbird]], [[libreoffice]]
Deletions:
Additions:
Download and install the software package file anywhere, and outside any personal save file, e.g. [[opera]], [[seamonkey]], [[thunderbird]] [[libreoffice]]
Deletions:
Additions:
===Software installation===
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.
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.
Deletions:
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.
Additions:
==Pre-requisites for software installation==
Deletions:
[[PPM Puppy Package Manager]]
[[SoftwarePackageCreation]]
Additions:
**Installing PET software packages**
- or, (B) follow the instructions at (does not require re-booting): //Menu > Setup > [[http://www.murga-linux.com/puppy/viewtopic.php?t=64354 SFS-Load]]//
- or, (B) follow the instructions at (does not require re-booting): //Menu > Setup > [[http://www.murga-linux.com/puppy/viewtopic.php?t=64354 SFS-Load]]//
Deletions:
- or, (B) follow the instructions at (does not require re-booting): //Menu > Setup > [[http://www.murga-linux.com/puppy/viewtopic.php?t=64354 SFS-Load]]//<<
Additions:
Other software package types:
Additions:
There are two main software package types, identified by their file extension:
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.
[[http://murga-linux.com/puppy/viewtopic.php?p=489219#489219 How to upgrade the default software]]
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.
[[http://murga-linux.com/puppy/viewtopic.php?p=489219#489219 How to upgrade the default software]]
Deletions:
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.
[[http://murga-linux.com/puppy/viewtopic.php?p=489219#489219 Upgrading existing software]]
Deletions:
Additions:
Software package download location:
Deletions:
Additions:
Official software packages are available via the Puppy Package Manager:
Software package types are identified by their file extension:
[[http://murga-linux.com/puppy/viewtopic.php?p=489219#489219 Upgrading existing software]]
Software package types are identified by their file extension:
[[http://murga-linux.com/puppy/viewtopic.php?p=489219#489219 Upgrading existing software]]
Deletions:
More software packages can be added automatically via the Puppy Package Manager and QuickPet/Slickpet (later versions).
These are accessed via the relevant desktop icon or by the [[PuppyStartMenu Puppy start menu]]:
- //Menu > Setup > [[QuickPet]]//
- [[Squashfs SFS]] (all in one compressed packages) Menu/System/BootManager configure bootup
====About Puppy Software====
Puppy comes with [[SoftwareBuiltIn software built in]]. How much and which packages depends on the version of [[PuppyVersion Puppy]]. Typically, lightweight versions of the most popular software types are built in, for example [[AbiWord]] for word-processing, [[InkLite]] and [[mtPaint]] for graphics.
Other software can be download and installed automatically. Software package types are identified by their file extension:
"How does one upgrade existing software?"
[[http://murga-linux.com/puppy/viewtopic.php?p=489219#489219 forum topic]]
CategorySoftware
CategoryQuickStart
Additions:
Puppy comes with [[SoftwareBuiltIn software built in]]. How much and which packages depends on the version of [[PuppyVersion Puppy]]. Typically, lightweight versions of the most popular software types are built in, for example [[AbiWord]] for word-processing, [[InkLite]] and [[mtPaint]] for graphics.
Deletions:
Additions:
====About Puppy Software====
==Software Installation==
==Software Installation==
Deletions:
===Software Installation===
Additions:
CategoryQuickStart
Additions:
==Quick Start==
More software packages can be added automatically via the Puppy Package Manager and QuickPet/Slickpet (later versions).
- [[Squashfs SFS]] (all in one compressed packages) Menu/System/BootManager configure bootup
More software packages can be added automatically via the Puppy Package Manager and QuickPet/Slickpet (later versions).
- [[Squashfs SFS]] (all in one compressed packages) Menu/System/BootManager configure bootup
Deletions:
More software packages can be added automatically via the Puppy Package Manager and QuickPet (later versions).
Additions:
[[SoftwareDisclaimer]]
Additions:
[[HomePage]] > [[SoftwareIndex Software Index]]
Deletions:
Additions:
[[HomePage]] > [[SoftwareIndex]]
====Puppy Software====
Puppy comes with software built in. How much and which packages depends on the version of [[PuppyVersion Puppy]]. Typically, lightweight versions of the most popular software types are built in, for example [[AbiWord]] for word-processing, [[InkLite]] and [[mtPaint]] for graphics.
==Additional Software==
More software packages can be added automatically via the Puppy Package Manager and QuickPet (later versions).
These are accessed via the relevant desktop icon or by the [[PuppyStartMenu Puppy start menu]]:
Other software can be download and installed automatically. Software package types are identified by their file extension:
[[http://murga-linux.com/puppy/viewtopic.php?p=489219#489219 forum topic]]
==Also see==
[[PPM Puppy Package Manager]]
[[QuickPet]]
[[Pets Pet files]]
[[SquashFS SFS files]]
[[TXZfile TXZ files]]
[[SoftwarePackageCreation]]
CategorySoftware
====Puppy Software====
Puppy comes with software built in. How much and which packages depends on the version of [[PuppyVersion Puppy]]. Typically, lightweight versions of the most popular software types are built in, for example [[AbiWord]] for word-processing, [[InkLite]] and [[mtPaint]] for graphics.
==Additional Software==
More software packages can be added automatically via the Puppy Package Manager and QuickPet (later versions).
These are accessed via the relevant desktop icon or by the [[PuppyStartMenu Puppy start menu]]:
Other software can be download and installed automatically. Software package types are identified by their file extension:
[[http://murga-linux.com/puppy/viewtopic.php?p=489219#489219 forum topic]]
==Also see==
[[PPM Puppy Package Manager]]
[[QuickPet]]
[[Pets Pet files]]
[[SquashFS SFS files]]
[[TXZfile TXZ files]]
[[SoftwarePackageCreation]]
CategorySoftware
Deletions:
Software package types are identified by their file extension:
http://murga-linux.com/puppy/viewtopic.php?p=489219#489219
Deletions:
- http://dotpups.de/
- [[http://www.murga-linux.com/puppy/viewtopic.php?p=143732 Software from Sigmund Berglund]]
Additions:
Software packages are available via the Puppy start menu or the relevant desktop icon:
Software package types are identified by their file extension:
- **//.tar.xz//** or **//.txz//** (intended for all full and frugal Puppy installations)
- **//.pet//** (intended for all full and frugal Puppy installations)
- **//.sfs//** (intended for all frugal or LiveDVD installations)
Ensure that the latest available versions of the following packages are installed:
Software package types are identified by their file extension:
- **//.tar.xz//** or **//.txz//** (intended for all full and frugal Puppy installations)
- **//.pet//** (intended for all full and frugal Puppy installations)
- **//.sfs//** (intended for all frugal or LiveDVD installations)
Ensure that the latest available versions of the following packages are installed:
Deletions:
//Click on software name or icon to install//
**Software package types are identified by their file extension:**
- //.tar.xz// or //.txz// (intended for all full and frugal Puppy installations)
- //.pet// (intended for all full and frugal Puppy installations)
- //.sfs// (intended for all frugal or LiveDVD installations)
If installation fails, ensure you have the latest available versions of the following packages:
Additions:
Software packages available via Puppy start menu or via the quickpet desktop icon:
//Click on software name or icon to install//
**Software package types are identified by their file extension:**
If installation fails, ensure you have the latest available versions of the following packages:
//Click on software name or icon to install//
**Software package types are identified by their file extension:**
If installation fails, ensure you have the latest available versions of the following packages:
Deletions:
Software packages are available via the start menu:
Ensure that the latest available versions of the following pre-requisite packages are installed:
No Differences
No Differences
No Differences
Additions:
<<**Installing PET software packages**
- or, (B) follow the instructions at (does not require re-booting): //Menu > Setup > [[http://www.murga-linux.com/puppy/viewtopic.php?t=64354 SFS-Load]]//<<
- or, (B) follow the instructions at (does not require re-booting): //Menu > Setup > [[http://www.murga-linux.com/puppy/viewtopic.php?t=64354 SFS-Load]]//<<
Deletions:
- or, (B) follow the instructions at (does not require re-booting): //Menu > Setup > [[http://www.murga-linux.com/puppy/viewtopic.php?t=64354 SFS-Load]]//
Additions:
Acquire (download) the relevant PET software package then single-left-click on it. To reverse the process, i.e. to un-install PET software packages, go to the [[uninstalling un-installing]] page.
Deletions:
To un-install PET software packages go to the [[uninstalling un-installing]] page.
Additions:
To un-install PET software packages go to the [[uninstalling un-installing]] page.
Deletions:
- via the Puppy Package Manager: //Menu > Setup > Puppy Package Manager//
- via the command-line interface: http://www.murga-linux.com/puppy/viewtopic.php?p=396935#396935
Additions:
Software packages are available via the start menu:
Additions:
Acquire (download) the relevant PET software package then single-left-click on it, whilst observing the following conditions.
__Installing ''PET'' packages within frugal Puppy installations__
__Installing ''PET'' packages within full Puppy installations__
**Un-installing PET software packages**
- via the Puppy Package Manager: //Menu > Setup > Puppy Package Manager//
- via the command-line interface: http://www.murga-linux.com/puppy/viewtopic.php?p=396935#396935
__Installing ''PET'' packages within frugal Puppy installations__
__Installing ''PET'' packages within full Puppy installations__
**Un-installing PET software packages**
- via the Puppy Package Manager: //Menu > Setup > Puppy Package Manager//
- via the command-line interface: http://www.murga-linux.com/puppy/viewtopic.php?p=396935#396935
Deletions:
__Installing ''PET'' packages into frugal Puppy installations__
__Installing ''PET'' packages into full Puppy installations__
__Un-installing PET packages__
Go to: //Menu > Setup > Puppy Package Manager//
http://murga-linux.com/puppy/viewtopic.php?p=396935#396935
__[[http://www.murga-linux.com/puppy/viewtopic.php?p=396935#396935 Installing and un-installing PET packages via the command-line interface]]__
Additions:
__Installing ''PET'' packages into frugal Puppy installations__
__Installing ''PET'' packages into full Puppy installations__
__Installing ''PET'' packages into full Puppy installations__
Deletions:
__Installing ''PETs'' into full Puppy installations__
Additions:
[[compiling How to build (compile) a software package from the source code and install it]]
[[SoftwarePackageCreation How to create a software package for Puppy]]
Acquire (download) the relevant PET software package then single-left-click on it.
Download and install the software package file anywhere, and outside any personal save file, such as ///mnt/home//. Examples: [[opera]], [[seamonkey]], [[libreoffice]]
[[SoftwarePackageCreation How to create a software package for Puppy]]
Acquire (download) the relevant PET software package then single-left-click on it.
Download and install the software package file anywhere, and outside any personal save file, such as ///mnt/home//. Examples: [[opera]], [[seamonkey]], [[libreoffice]]
Deletions:
[[SoftwarePackageCreation How to Create a Software Package for Puppy]]
- 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
- download and install the software package file anywhere and outside any personal save file, such as ///mnt/home// (examples: [[opera]], [[seamonkey]], [[libreoffice]]
Additions:
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. 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//.
Deletions:
Additions:
[[DesktopIcons How to create desktop icons]]
Deletions:
DesktopIcons
Additions:
Software package names that contain a suffix 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//.
Deletions:
Deletions:
Additions:
**Installing TXZ software packages**
**Installing [[http://puppylinux.org/wikka/Squashfs SFS]] software packages**
**Installing [[http://puppylinux.org/wikka/Squashfs SFS]] software packages**
Deletions:
===Installing **[[http://puppylinux.org/wikka/Squashfs SFS]]** software packages===
Additions:
**Installing PET software packages**
Deletions:
Additions:
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//.
Deletions:
The suffix denotes 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//.
Deletions:
Additions:
==={{color text="Software Repositories" c="green"}}===
Software disclaimer: absolutely no warranty given or implied, so use any software package entirely at your own risk
----
==Categories==
CategoryInstallation
Software disclaimer: absolutely no warranty given or implied, so use any software package entirely at your own risk
----
==Categories==
CategoryInstallation
Deletions:
==={{color text="Un-official Software Repositories" c="green"}}===
===Software Disclaimer===
**absolutely no warranty given or implied, so use any software package entirely at your own risk**
Additions:
- download and install the software package file anywhere and outside any personal save file, such as ///mnt/home// (examples: [[opera]], [[seamonkey]], [[libreoffice]]
- download and place the software package file at ///mnt/home// (examples: [[JavaRuntimeEnvironment jre]])
- download and place the software package file at ///mnt/home// (examples: [[JavaRuntimeEnvironment jre]])
Deletions:
- download and place the software package file at ///mnt/home//: %%wget -t 0 --retry-connrefused -c -N -S -T 16 -w 1 --random-wait --no-dns-cache -P /mnt/home --no-cache --no-cookies http://path/to/software_package.sfs%%
Additions:
- download and install the software package file anywhere and outside any personal save file, e.g. ///mnt/home//: %%wget -t 0 --retry-connrefused -c -N -S -T 16 -w 1 --random-wait --no-dns-cache -P /mnt/home --no-cache --no-cookies http://path/to/software_package.txz && cd /mnt/home && tar xfJv software_package.txz%%
Deletions:
Additions:
- download and install the software package file anywhere and outside any personal save file, e.g. ///mnt/home//: %%wget -t 0 --retry-connrefused -c -N -S -T 16 -w 1 --random-wait --no-dns-cache -P /mnt/home --no-cache --no-cookies http://path/to/software_package.txz && cd /mnt/home && tar xfJv software_package.txz%%
Deletions:
- extract the software package: %%tar xfJv software_package.txz%%
Deletions:
Additions:
__[[http://www.murga-linux.com/puppy/viewtopic.php?p=396935#396935 Installing and un-installing PET packages via the command-line interface]]__
Deletions:
Additions:
==={{color text="Official Software Repositories" c="green"}}===
==={{color text="Un-official Software Repositories" c="green"}}===
==={{color text="Un-official Software Repositories" c="green"}}===
Deletions:
==={{color text="Un-official Puppy Repositories" c="green"}}===
Additions:
Also accessible via the start menu, using one or both of these methods:
- //Menu > Setup > [[PPM Puppy Package Manager]]//
- //Menu > Setup > [[QuickPet]]//
- //Menu > Setup > [[PPM Puppy Package Manager]]//
- //Menu > Setup > [[QuickPet]]//
Deletions:
- either, //Menu > Setup > [[PPM Puppy Package Manager]]//
- or, //Menu > Setup > [[QuickPet]]//
