"Fossies" - the Fresh Open Source Software Archive

Member "ext3undel-0.1.6/doc/install.txt" (12 Jun 2008, 3173 Bytes) of package /linux/misc/old/ext3undel-0.1.6.tar.gz:

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 Installation with make
    2 ======================
    4 When you downloaded the tarball of this software, after unpacking you will find
    5 a file called "Makefile" in the packages root directory. This means, there's
    6 something you can do with an utility called "make" - which normally is used in
    7 the build process for compiling source code to binaries. It can be (and also is)
    8 used for (un)installation of the (compiled) software - and that's what this
    9 document is about.
   11 Please keep in mind that the Makefile was written for use with Linux. So this
   12 process will probably work with other Unix alike systems (*BSD, Solaris, AIX,
   13 etc.) as well - but for sure not with e.g. Windows (except maybe with Cygwin).
   15 Configuration
   16 -------------
   18 As shipped, the configuration usually is such that the files would be installed
   19 as follows:
   21 Executables go to /usr/local/bin
   22 Configuration files go to /etc
   23 Documentation goes to /usr/local/share/doc/<packagename>
   25 For web apps, the installation goes to /usr/local/share/<packagename>, and this
   26 directory will be linked to /var/www/<packagename> - if this directory/file/link
   27 does not yet exist.
   29 If you want to install to a different location, you may change some variables at
   30 the top of the Makefile. Usually, these are:
   32 prefix=/usr/local		Path for the executables is derived from this
   33 datarootdir=$(prefix)/share	Path for webapps and documentation uses this
   34 sysconfdir=/etc			Path for configuration files
   35 WEBROOT=/var/www		Just for webapps: Where to create a link
   37 You may as well check the other settings, but these three are the most
   38 important for you. You could also override these on the command line, e.g.
   39 with "make prefix=/opt install" - but I don't recommend that if you want to
   40 run a "make uninstall" later, since you may forget what options you used on the
   41 install.
   44 Installation
   45 ------------
   47 Once the configuration is done, installation is as easy as invoking
   49 	make install
   51 from within the directory where the Makefile resides. As mentioned above, you
   52 also can override some configuration options here:
   54 	make prefix=/opt install
   56 for example. But keep in mind that you need to remember these settings for the
   57 case you want to uninstall later.
   60 Uninstall
   61 ---------
   63 is pretty much alike the install process. From the directory where the Makefile
   64 resides, simply invoke:
   66 	make uninstall
   68 or, if you were overriding some options when calling "make install", you need
   69 to specify the same here:
   71 	make prefix=/opt uninstall
   73 The uninstall process will remove everything it has installed - but nothing that
   74 you created yourself later (usually; if you e.g. added a file to the
   75 documentation directory in /usr/local/share/doc/<packagename>, this will be
   76 removed as well since we remove the entire directory. You are not expected to
   77 do modifications here) using this application, as e.g. template files, or
   78 "personal" configuration files you created in your home directory.
   81 Alternatives
   82 ------------
   84 Alternatively you can manually (un)install the package. Hints for this you
   85 usually find in another file from the packages documentation - most likely one
   86 named readme.txt or <packagename>.txt and residing in the doc/ sub directory.