-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
77 lines (60 loc) · 2.06 KB
/
README
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
servicelog:
-----------
The servicelog package contains command line interfaces for viewing and
manipulating the contents of the servicelog database. Servicelog contains
entries that are useful for performing system service operations, and for
providing a history of service operations that have been performed on the
system.
Source:
-------
http://linux-diag.sf.net/servicelog.html
Mailing list:
-------------
Info/subscribe : https://lists.sourceforge.net/lists/listinfo/linux-diag-devel
License:
--------
See 'COPYING' file.
Compilation dependencies:
-------------------------
- C compiler (gcc)
- GNU build tools (automake, autoconf, libtool, etc)
- libservicelog-devel
Binary dependencies:
-------------
- libservicelog
Note:
- Package name may differ slightly between Linux distributors. Ex: RedHat and
SLES ships development packages as "-devel" while Ubuntu ships it as "-dev"
package. Please check your linux distribution package naming convention and
make sure you have installed right packages.
Building:
---------
You can build on Power Linux system.
$ ./bootstrap.sh
$ ./configure [--prefix=/usr/]
$ make
$ make install
Building rpms:
--------------
To build a tarball to feed to rpmbuild, do
$ make dist-gzip
As an example, we use a command similar to the following:
$ rpmbuild -ba [--target=ppc/ppc64] <path-to-spec-file>
Hacking:
--------
All patches should be sent to the mailing list with linux-kernel style
'Signed-Off-By'. The following git commands are your friends:
- git commit -s
- git format-patch
You probably want to read the linux Documentation/SubmittingPatches as
much of it applies to libservicelog.
Submitting patch:
-----------------
We use same mailing list for all Power Linux VPD and diagnostics projects
(ppc64-diag, libvpd, lsvpd, [lib]servicelog). It is common convention to
prefix your subject line with project name. This lets maintainer and other
developers more easily identify patches from patches targeted to other
projects. For example,
Subject: [servicelog PATCH 01/10] Summary phrase
--