| IndexA
- absolute package
, - traditional example
,
- administrative defaults file
,
- archive packages
- creating
, - directory structure
, - keywords
,
- awk class
, - script
,
B
- base directory
, , - in the administrative defaults file
, - using parametric path names
, - using the BASEDIR parameter
, - walking the
, , - example
, ,
- build class
, - in a case study
, - script
, - in a case study
,
- build time
,
- build variable
- description
,
- building a package
, - the process
,
- bundled packages
,
C
- checking package installation
, - the process
,
- checkinstall script
, , , , , , , , , - and environment variables
, - design rules
, - how to write a
, - writing a
,
- clarch
,
- class action script
, , , , , , - behaviors
, - design rules
, - how to write a
, - in a case study
, , , , , , - naming conventions
,
- classes
- See object classes
- collectively relocatable object
, ,
- composite
,
- composite package
- example
, , , - rules for constructing
, - traditional example
,
- compver file
, - description
, - example
, - how to write
, - in a case study
,
- control files
- description
- See also information files and installation scripts
- copyright file
, - example
, - how to write
, - in a case study
, , - writing a
,
D
- depend file
, - description
, - example
, - how to write
, - in a case study
,
E
- exit codes for scripts
,
F
- faspac utility
,
G
- guidelines, packaging
,
I
- incompatible package
,
- individually relocatable object
, ,
- install time
,
- install variable
- description
,
- installation environment variables
,
- installation scripts
- and environment variables
, - characteristics
, - creating
, - exit codes
, - obtaining package information
, - processing of
, - requirements for
, - types of
, ,
- installation software database
,
- installf command
, , - in a case study
, ,
- installing classes
,
- installing packages on a standalone or server
- example
,
- installing packages to clients
- example
,
| |