]> git.pld-linux.org Git - packages/cfg.git/blame - cfg.spec
- added proper requires between subpackages
[packages/cfg.git] / cfg.spec
CommitLineData
f9c56c65 1# TODO: resolve conflict with libcfg+-devel - header files
2# has the same name.
3# NOTE: API is NOT documented
4Summary: OSSP cfg - Configuration Parsing
5Summary(pl): OSSP cfg - parsowanie konfiguracji.
6Name: cfg
7Version: 0.9.4
8Release: 0.1
9License: distributable (see README)
10Group: Libraries
11Source0: ftp://ftp.ossp.org/pkg/lib/cfg/%{name}-%{version}.tar.gz
12# Source0-md5: a41ac64a92a55030f44e307cc5461657
13URL: http://www.ossp.org/pkg/lib/cfg/
14BuildRequires: autoconf
2e487087 15BuildRequires: automake
f9c56c65 16BuildRequires: bison
17BuildRequires: flex
18BuildRequires: libtool
19Requires(post,postun): /sbin/ldconfig
20BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n)
21
22%description
23OSSP cfg is a ISO-C library for parsing arbitrary C/C++-style
24configuration files. A configuration is sequence of directives. Each
25directive consists of zero or more tokens. Each token can be either a
26string or again a complete sequence. This means the configuration
27syntax has a recursive structure and this way allows to create
28configurations with arbitrarily nested sections.
29
30Additionally the configuration syntax provides complex
31single/double/balanced quoting of tokens, hexadecimal/octal/decimal
32character encodings, character escaping, C/C++ and Shell-style
33comments, etc. The library API allows importing a configuration text
34into an Abstract Syntax Tree (AST), traversing the AST and optionally
35exporting the AST again as a configuration text.
36
37#%%description -l pl
38# I need API documentation instead pl description.
39
40%package devel
41Summary: OSSP cfg - Configuration Parsing - header files and development libraries
42