cpset(C)                      06 January 1993                       cpset(C)


 Name

    cpset - install object files in binary directories

 Syntax

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

 Description

    cpset is used to install the specified object file, object in the direc-
    tory, directory.  The mode, owner, and group of the file, object, may be
    specified on the command line.  If these parameters are omitted, there
    are two possible results:

    +  If cpset is run by a user who 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 does not have administrator permissions, the default,
       owner, and group of the destination file will be those of the user.

    The -o argument forces cpset to move object to OLDobject in the destina-
    tion directory before installing the new object file.

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

 Examples

    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 des-
    tination of a file.  The locations file contains pairs of pathnames
    separated by spaces or tabs.  The first name is the ``official'' destina-
    tion (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 occurs, 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 pro-
    cedures used to build the source will be responsible for defining the
    ``official'' locations of the source.

 See also

    install(ADM), make(CP)

 Standards conformance

    cpset is conformant with AT&T SVID Issue 2.