Installing Ipkgs - VeriFone MX800 series Programmer's Manual

Version
Architecture
Maintainer
Description
Priority
Section
Depends

Installing ipkgs

The ipkg files (.pkg extension) can be placed in the terminal similar to how .TAR
files are placed. If the terminal is locked/deployed, the .PKG file is signed,
downloaded and installed in the same manner as an application .TAR file.
If the terminal is unlocked (such as during development), the user has the option
of manually installing/removing packages. Once the pkg file is in /home/usr1,
the user can execute: ipkg install package.PKG where package.PKG is
the file name of the package to be installed. To remove a previously installed
package, execute: ipkg remove package where package is the "name" of the
package as specified in the control file (to get a list of the installed packages,
execute: ipkg list_installed).
should have at least one digit and should match "[a-zA-Z0-9.+]*".
Version may also contain an optional trailing revision matching "-fam[0-
9]\+". This revision should be incremented each time the package
changes but the version does not, (i.e. a packaging tweak). It may be
reset, (or simply omitted), each time the version is incremented.
should specify the architecture for which the package is compiled. Valid
values currently include: arm, i386, m68k, ns32k, sh3, sparc, vax,
and all.
should be the name and email address of the person responsible for
maintaining the package, (not necessarily the author of the program).
should be a short, (less than 80 characters) description of the program.
It may also include a long description on subsequent lines, (each
indented by a single space character). Blank lines in the long description
may be indicated by a line consisting of a space character followed by a
period, i.e. " ."
should be one of: required, standard, important, optional, or extra. Most
programs should use optional.
can be one of the following: admin, base, comm, editors, extras,
graphics, libs, misc, net, text, web, x11.
indicates packages which must also be installed in order for this
package to work. The packages should be listed on a single line,
separated by commas.
Package Management
X
M 800 S P
ERIES ROGRAMMERS
F S
ILE YSTEMS
31
G
UIDE