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
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
1 Installation on UNIX systems
1.1 Direct installation from source
1.2 Installation via RPM
1.3 Installation via DEB
2 Installation on Windows systems
1 Installation on UNIX systems
==============================
1.1 Direct installation from source
-----------------------------------
After unpacking the software change into the source directory and run
./configure
make
make install
For help on configure script options, run
./configure --help
If you have LPRng installed and you want to use printqd, see the
``CONFIGURATION'' section in printqd(1). Some directories may need
ownership and permissions correction.
1.2 Installation via RPM
------------------------
If you are building a package for an ``official'' Linux distribution:
If the distribution includes the LPRng software, find user and group name
used to run the LPRng lpd daemon and activate and correct LPUSER and
LPGROUP in the dktools.spec file in the LINUX DISTRIBUTION PACKAGERS section.
Manual steps
~~~~~~~~~~~~
The archive contains *.spec files for Scientific Linux (should work on
other Enterprise Linux clones too) and Fedora core.
Copy the *.spec file to ~/rpmbuild/SPECS and the dktools-*.tar.gz file
to ~/rpmbuild/SOURCES.
Change into the ~/rpmbuild/SPECS directory and run
rpmbuild -ba dktools.spec
You must be root to install the *.rpm file, change into the
rpmbuild/RPMS/<architecture> directory and run
rpm --force -Uhv dktools-<version>-.rpm dktools-debuginfo-<version>.rpm
Use scripts
~~~~~~~~~~~
The scripts below were created and tested on Scientific Linux 6.
As root run
./sl6-prepare.sh
to install development tools and development files for required libraries.
As non-privileged user run
./sl6-build-rpm.sh
to build the RPM file.
1.3 Installation via DEB
------------------------
The archive contains a ``debian'' subdirectory and two scripts to create
a *.deb package. The scripts were created and tested on Debian Jessie.
If you are building a package for an ``official'' Linux distribution:
If the distribution includes the LPRng software, find user and group name
used to run the LPRng lpd daemon and activate and correct LPUSER and
LPGROUP in the debian/postinst file
in the LINUX DISTRIBUTION PACKAGERS section.
As root run:
./debian-jessie-prepare.sh
to install required packages (development tools, development packages
for used libraries).
As non-privileged user run:
./debian-jessie-build-deb.sh
to build the *.deb files.
You should find several *.deb files in the parent directory:
(1) dktools-lib-data_x.y.z-1_all.deb
Data files for the DK tools shared libraries.
(2) dktools-data_x.y.z-1_all.deb
Data files for the DK tools programs.
(3) dktools-lib-x.y_x.y.z-1_arch.deb
The DK tools shared libraries.
(4) dktools_x.y.z-1_arch.deb
The DK tools programs (requires 1, z, and y).
(5) dktools-dev_x.y.z-1_arch.deb
DK tools developer support (requires 1, 2, and 3).
On normal systems install (1), (2), (3), and (4). For development install
(5) too.
2 Installation on Windows systems
=================================
Windows users should obtain dktools-win64-*.exe from the dktools project
at SourceForge, see
http://sourceforge.net/projects/dktools
for the download.
Run the installer and follow the instructions.
See http://dktools.sourceforge.net/install.html for details about the
installation process.
|
