forked from power-ras/servicelog
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME
80 lines (64 loc) · 2.29 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
78
79
80
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:
-------
https://github.com/power-ras/servicelog
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>
Reporting issue:
----------------
Create a GitHub issue if you have any request for change, assuming one does
not already exist. Clearly describe the issue including steps to reproduce
if it is a bug.
How to contribute:
------------------
If you plan to submit the changes, submit a pull request based on top of
master. Include a descriptive commit message. Changes contributed should
focus on a single issue at a time to the extent possible.
Hacking:
--------
The following workflow should work for you:
- Fork the repository on GitHub into your account.
- Create a topic branch from where you want to base your work.
This is usually the master branch.
- Make sure you have added the necessary tests for your changes and make sure
all tests pass.
- Push your changes to the topic branch in your fork of the repository.
- Include a descriptive commit message, and each commit should have
linux-kernel style 'Signed-Off-By'.
- Submit a pull request to this repository.
You probably want to read the linux Documentation/SubmittingPatches as
much of it applies to libservicelog.
--