current/SPECS/erlang-setup.spec

%global realname setup
%global upstream uwiger


Name:           erlang-%{realname}
Version:        2.0.2
Release:        1%{?dist}
BuildArch:      noarch
Summary:        Generic setup utility for Erlang-based systems
License:        ASL 2.0
URL:            https://github.com/%{upstream}/%{realname}
VCS:            scm:git:https://github.com/%{upstream}/%{realname}.git
Source0:        https://github.com/%{upstream}/%{realname}/archive/%{version}/%{realname}-%{version}.tar.gz
Patch1:         erlang-setup-0001-Don-t-escriptize.patch
Patch2:         erlang-setup-0002-Support-expansion-of-setup-modes-for-find_hooks.patch
BuildRequires:  erlang-rebar
Group:          Development/Tools

%description
While Erlang/OTP comes with many wonderful applications, including the Mnesia
DBMS, there is no standard or convention for installing a system. Erlang/OTP
provides tools for building a boot script, and rules for setting environment
variables, etc., and Mnesia offers an API for creating and modifying the
database schema.

However, with no convention for when these tools and API functions are called -
and by whom - application developers are left having to invent a lot of code
and scripts, not to mention meditate over chapters of Erlang/OTP documentation
in order to figure out how things fit together.

This utility offers a framework for initializing and configuring a system, with
a set of conventions allowing each component to provide callbacks for different
steps in the installation procedure.

The callbacks are defined through OTP application environment variables, which
can easily be overriden at install time.


%prep
%autosetup -p1 -n %{realname}-%{version}


%build
%{erlang_compile}


%install
%{erlang_install}


%check
%{erlang_test}


%files
%doc doc/ examples/ README.md
%{erlang_appdir}/
1	joequant	1668709	%global realname setup
2			%global upstream uwiger
3
4
5			Name: erlang-%{realname}
6			Version: 2.0.2
7			Release: 1%{?dist}
8			BuildArch: noarch
9			Summary: Generic setup utility for Erlang-based systems
10			License: ASL 2.0
11			URL: https://github.com/%{upstream}/%{realname}
12			VCS: scm:git:https://github.com/%{upstream}/%{realname}.git
13			Source0: https://github.com/%{upstream}/%{realname}/archive/%{version}/%{realname}-%{version}.tar.gz
14			Patch1: erlang-setup-0001-Don-t-escriptize.patch
15			Patch2: erlang-setup-0002-Support-expansion-of-setup-modes-for-find_hooks.patch
16			BuildRequires: erlang-rebar
17			Group: Development/Tools
18
19			%description
20			While Erlang/OTP comes with many wonderful applications, including the Mnesia
21			DBMS, there is no standard or convention for installing a system. Erlang/OTP
22			provides tools for building a boot script, and rules for setting environment
23			variables, etc., and Mnesia offers an API for creating and modifying the
24			database schema.
25
26			However, with no convention for when these tools and API functions are called -
27			and by whom - application developers are left having to invent a lot of code
28			and scripts, not to mention meditate over chapters of Erlang/OTP documentation
29			in order to figure out how things fit together.
30
31			This utility offers a framework for initializing and configuring a system, with
32			a set of conventions allowing each component to provide callbacks for different
33			steps in the installation procedure.
34
35			The callbacks are defined through OTP application environment variables, which
36			can easily be overriden at install time.
37
38
39			%prep
40			%autosetup -p1 -n %{realname}-%{version}
41
42
43			%build
44			%{erlang_compile}
45
46
47			%install
48			%{erlang_install}
49
50
51			%check
52			%{erlang_test}
53
54
55			%files
56			%doc doc/ examples/ README.md
57			%{erlang_appdir}/