Browse Prior Art Database

Using Filepackage Objects to Handle Packaging of Files for Installation

IP.com Disclosure Number: IPCOM000116255D
Original Publication Date: 1995-Aug-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 62K

Publishing Venue

IBM

Related People

Greenlee, KL: AUTHOR [+5]

Abstract

The simplest way to package files for installation is to copy them as they are onto the installation media. This works fine if you have a small number of files and an installation media large enough to hold them all. But, if you have many files to be packaged that require multiple media, or large files bigger than your media, then it is necessary to compress the files together to use as little physical media space as possible. FILEPACKAGE objects will address these problems.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 53% of the total text.

Using Filepackage Objects to Handle Packaging of Files for Installation

      The simplest way to package files for installation is to copy
them as they are onto the installation media.  This works fine if you
have a small number of files and an installation media large enough
to hold them all.  But, if you have many files to be packaged that
require multiple media, or large files bigger than your media, then
it is necessary to compress the files together to use as little
physical media space as possible.  FILEPACKAGE objects will address
these problems.

      Most products contain related files like EXEs, DLLs, LIBs,
HLPs, etc..  Usually, these individual file sets need to be installed
together to the same locations.  It is in packaging these file sets
where we need FILEPACKAGES.

      By compressing files together into a single file and creating
FILEPACKAGE objects, we not only save space but we can also save time
by transferring fewer files across the network for remote installs.
Additionally, we can easily handle files larger than our physical
media, by splitting FILEPACKAGES.  The FILEPACKAGE represents a
physical grouping of files that have the following attributes in
common:
  o  target path
  o  contained media
  o  preload/non-preload
  o  compression type

      A single source file with a single target path will not be
compressed, but will become its own FILEPACKAGE.  Any FILEPACKAGE
that is too large for a single media can be split into two
FILEPACKAGES.  To control the FILEPACKAGES there are the following
attributes and methods:
  Figure.  FilePackage Class Attributes and Methods.
  ATTRIBUTES:
  PSZTAG                        This objects tag name
  PSZTYPE                       This objects type
  BSELECTED                     Selected or not flag
  BPLACED                       Whether placed on media or not flag
  BINSTALLED                    Whether files in FilePackage
installed
                                 or not
  PSZFILENAME       ...