Skip to content

anupkumk/libservicelog

 
 

Repository files navigation

libservicelog:
--------------
The libservicelog package contains a library to create and maintain a database
for storing events related to system service. This database allows for the
logging of serviceable and informational events, and for the logging of service
procedures that have been performed upon the system.

Source:
------
https://github.com/power-ras/libservicelog

License:
--------
See 'COPYING' file.

Compilation dependencies:
-------------------------
- C and C++ compiler (gcc, g++)
- GNU build tools (automake, autoconf, libtool, etc)
- librtas-devel
- sg3_utils-devel
- flex
- bison

Binary dependencies:
-------------
- sqlite3
- librtas

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.

--

About

libservicelog

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C 94.1%
  • Yacc 2.2%
  • Shell 1.8%
  • Other 1.9%