1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
TkMan has been built successfully by many people on many different
flavors of UNIX, including these: SunOS, Sun Solaris, Hewlett-Packard
HP-UX, AT&T System V, OSF/1, DEC Ultrix, SGI IRIX, Linux, SCO, IBM
AIX, FreeBSD, BSDI. Before you report a problem in getting TkMan
installed on your machine, double check that you haven't overlooked
something important in the Makefile. And check the home site
(ftp://ftp.cs.berkeley.edu/ucb/people/phelps/tcltk/tkman.tar.Z) to
make sure you're working with the latest version.
Before reporting a bug, first check the home site to make sure you're
using the latest version of TkMan. If you send me bug reports and/or
suggestions for new features, include your MANPATH, the versions of
TkMan, Tcl, Tk, X, and UNIX, your machine and X window manager names,
the edited Makefile, a copy of your ~/.tkman file, and the first few
lines of the `tkman' executable. I'd also be interested in learning
where you obtained TkMan.
*** INSTALLING ***
TkMan 2.0 is based on Tcl/Tk 8.0 and will not work with earlier
versions. Tcl and Tk are available for anonymous ftp from
ftp.smli.com. TkMan expects a UNIX-like man page directory structure.
Be sure to read through the Makefile as there are pieces throughout
the top half of it that you may wish or need to customize for your
site. Set BINDIR in the Makefile to where you keep your binaries (the
`tkman' script goes here). After properly editing the Makefile, type
`make install'. Thereafter type `tkman' to invoke TkMan (perhaps
after a `rehash').
SUN SOLARIS, SGI IRIX, SCO, IBM AIX, BSDI
These systems store manual pages in nonstandard ways. Each of
Solaris, SGI IRIX and SCO requires a special bindings file found in
the contrib directory. TkMan automatically installs the appropriate
binding file for new users (those without a ~/.tkman startup file);
otherwise one can manually integrate the bindings into an existing
startup file. Random System V based OS'es should follow the example
for SGI. IBM AIX'ers should convert InfoExplorer format man pages to
the standard /usr/man/cat* format using the procedure described in
section 7 of the document /usr/lpp/bos/bsdadm or in the FAQ for the
comp.unix.aix newsgroup. BSDI users should replace makewhatis with
some freely available version of mkwhatis--one that puts whatis files
in the right place, though this isn't essential (don't ask me where to
find such a mkwhatis; check archie for freely available man page tool
suites)
--------------------------------------------------
Be sure to look in the contrib directory for lots of good stuff.
--------------------------------------------------
Copyright (c) 1993-1997 Regents of the University of California
Permission to use, copy, modify, and distribute this software and its
documentation for educational, research, internal corporate and
non-profit purposes, without fee, and without a written agreement is
hereby granted for all cases that do not conflict with the restriction
in the first sentence of this paragraph, provided that the above
copyright notice, this paragraph, and the following three paragraphs
appear in all copies.
Permission to incorporate this software into commercial products may
be obtained from the Office of Technology Licensing, 2150 Shattuck
Avenue, Suite 510, Berkeley, CA 94704.
IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY
FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF
THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE
PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF
CALIFORNIA HAS NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.
|
