Lines Matching refs:package

77 you need to run programs that are a part of your package during the
248 that is only recommended.  If the package is set up so that it is
370 install their data under @file{$(libexecdir)/@var{package-name}/},
372 @file{$(libexecdir)/@var{package-name}/@var{machine}/@var{version}}.
420 install their data under @file{$(datadir)/@var{package-name}/}.
446 need to modify files in this directory to configure the package's
455 types of files, if your program has them.  Every GNU package should
485 A package should not replace an existing header in this directory unless
486 the header came from the same package.  Thus, if your Foo package
490 package.
492 To tell whether @file{foo.h} came from the Foo package, put a magic
497 this package.  By default, it should be
505 The directory for installing the Info files for this package.  By
532 The directory for installing any Emacs Lisp files in this package.  By
547 package.  By default, it should be @file{/usr/local/share/locale}, but
558 package.  It will normally be @file{/usr/local/share/man}, but you
584 Use these names instead of @samp{manext} if the package needs to install man
673 menu entry for the given Info file; it is part of the Texinfo package.
708 package, if that format is desired.  GNU prefers Info files, so these
714 such as @code{htmldir}.  As one example, if your package has multiple
741 But if the package installs scripts as well as real executables, the
801 the package, not by ordinary users.  You may need special tools to
838 users build the package, ordinarily Make will not update the Info files
879 name which is the name of the package it is a distribution for.  This
922 this; you can find it in the Texinfo package.
965 from the package they belong to.
977 solely from the package being installed.  It is a post-installation
979 installs the package's Info files.
1040 of making binary packages.  Typically a binary package contains all the
1043 installation commands.  But installing the binary package does need to