Lines Matching full:installing
260 basic command for installing a file into the system.
347 The directory for installing executable programs that users can run.
354 The directory for installing executable programs that can be run from
363 The directory for installing executable programs to be run by other
408 The directory for installing idiosyncratic read-only
423 The directory for installing read-only data files that pertain to a
438 The directory for installing architecture-independent data files which
444 The directory for installing data files which the programs modify while
454 These variables specify the directory for installing certain specific
462 The directory for installing header files to be included by user
469 @file{/usr/local/include}. So installing the header files this way is
477 The directory for installing @samp{#include} header files for use with
496 The directory for installing documentation files (other than Info) for
505 The directory for installing the Info files for this package. By
515 Directories for installing documentation files in the particular
532 The directory for installing any Emacs Lisp files in this package. By
546 The directory for installing locale-specific message catalogs for this
557 The top-level directory for installing the man pages (if any) for this
563 The directory for installing section 1 man pages. Write it as
566 The directory for installing section 2 man pages. Write it as
650 Do not strip executables when installing them. Devil-may-care users can
656 program under one user name and installing it under another.
665 Use @samp{-} before any command for installing a man page, so that
707 they're intended to be called explicitly by the person installing the
731 Like @code{install}, but strip the executable files while installing
1042 method of installing them---so it does not need to run the normal
1043 installation commands. But installing the binary package does need to
