NAME

cpset − install object files in binary directories

SYNOPSIS

cpset [-o] object directory [ mode [ owner [ group ] ] ]

DESCRIPTION

Cpset is used to install the specified object file in the given directory. The mode, owner, and group, of the destination file may be specified on the command line. If this data is omitted, two results are possible:

If the user of cpset has administrative permissions (that is, the user’s numerical ID is less than 100), the following defaults are provided:

mode − 0755
owner − bin
group − bin

If the user is not an super-user, the default mode, owner, and group of the destination file will be that of the invoker. 

An optional argument of −o will force cpset to move object to OLDobject in the destination directory before installing the new object. 

For example:

cpset echo /bin 0755 bin bin

cpset echo /bin

cpset echo /bin/echo

All the examples above have the same effect (assuming the user is an administrator).  The file echo will be copied into /bin and will be given 0755, bin, bin as the mode, owner, and group, respectively. 

Cpset utilizes the file /usr/src/destinations to determine the final destination of a file.  The locations file contains pairs of pathnames separated by spaces or tabs.  The first name is the "official" destination (for example: /bin/echo).  The second name is the new destination.  For example, if echo is moved from /bin to /usr/bin, the entry in /usr/src/destinations would be:

/bin/echo/usr/bin/echo

When the actual installation happens, cpset verifies that the "old" pathname does not exist.  If a file exists at that location, cpset issues a warning and continues.  This file does not exist on a distribution tape; it is used by sites to track local command movement.  The procedures used to build the source will be responsible for defining the "official" locations of the source. 

Cross Generation

The environment variable ROOT will be used to locate the destination file (in the form $ROOT/usr/src/destinations).  This is necessary in the cases where cross generation is being done on a production system. 

SEE ALSO

install(1M), make(1). 

Hewlett-Packard Company  —  May 11, 2021