"Fossies" - the Fresh Open Source Software Archive

Member "courier-1.2.2/README" (25 Aug 2013, 2075 Bytes) of package /linux/misc/courier-1.2.2.tar.bz2:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 Read INSTALL for installation instructions.
    2 
    3 Better yet, read courier/doc/install.html, which is the same thing, but in
    4 a much more readable HTML.
    5 
    6 If you got this from CVS, you don't have an INSTALL, because it is created
    7 from install.html during make dist.  You will need to read
    8 README.CVS, then courier/doc/install.html.
    9 
   10 configure --help will not show anything useful.  You must read INSTALL to
   11 know what options to use.
   12 
   13 If you are packaging or porting Courier, the install-perms Makefile target
   14 might be very useful.  It creates permissions.dat, listing the location of
   15 everything that make install or make install-strip would install, including
   16 permission and ownership of each file, as well as an indicator if it's a
   17 manual page, configuration file, or a documentation file.   It's used by
   18 courier.spec, which is generated in the top level directory.  It's an
   19 RPM spec script.  Browse through it for a feel of how to use permissions.dat.
   20 
   21 If you are packaging or porting Courier, examine install.html thoroughly.
   22 In almost every case you will need to specify several non-default options.
   23 Be prepared to have to rebuild at least a couple of times.
   24 
   25 After installation, you should arrange for /usr/lib/courier/bin (or wherever
   26 it's installed) to be added to everyone's path, and /usr/lib/courier/man added
   27 to everyone's MANPATH.
   28 
   29 Starting with version 0.30, the installation script has a new target:
   30 "make install-configure" that installs the new configuration files,
   31 preserving the previous configuration.
   32 
   33 If you're creating a package, do not run 'make install-configure'.  Instead,
   34 package everything after running 'make install'.  Run 'make install-perms'
   35 to create permissions.dat, and extract the names of all *.dist files in
   36 permissions.dat that are also marked 'config'.  After your package is
   37 installed, have the installation script run the 'sysconftool' script and
   38 provide the list of files as the arguments to 'sysconftool'.
   39 
   40 Basically, see the 'install-configure' target in Makefile.am, and have that
   41 done after installation, instead of during packaging.
   42