# Generated from coral-0.5.0.gem by gem2rpm -*- rpm-spec -*-
%global gem_name coral

Name: rubygem-%{gem_name}
Version: 0.5.0
Release: 1%{?dist}
Summary: Alternative gem name for the CORL system
License: Apache License, Version 2.0
URL: http://github.com/coraltech/coral
Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
BuildRequires: ruby(release)
BuildRequires: rubygems-devel
BuildRequires: ruby >= 1.9.1
# BuildRequires: rubygem(jeweler) >= 2.0
# BuildRequires: rubygem(jeweler) < 3
# BuildRequires: rubygem(rspec) >= 2.10
# BuildRequires: rubygem(rspec) < 3
# BuildRequires: rubygem(yard) >= 0.8
# BuildRequires: rubygem(yard) < 1
# BuildRequires: rubygem(vagrant) >= 1.5
BuildArch: noarch

%description
== coral
This gem is simply a meta package that installs and requires the CORL gem.
Note:  CORL is still early in development!
DO NOT USE IN PRODUCTION YET!!
Now you get to hear the story of two names.
Short story first;  We switched to the CORL name (github.com/coralnexus/corl).
If your interested in why:
The original name of the CORL project was Coral, and we were exited when we
found 
the Ruby gem name "coral" available.  Our first versions of our CORL system
were
named coral_core, coral_cloud, coral_vagrant, coral_plan, and many more were
planned.
We created a meta gem (this one) to install a core combination of gems.  
During the course of development we found another project that came before
ours that 
uses the name coral, so we decided to update our project name, so as to avoid
conflicts.
For us Coral is more than a word, it is a concept that embodies dynamic
ecosystems 
supporting a rich variety of lifeforms.  Coral are very interesting creatures
and we
endeavor to create software that helps build dynamic ecosystems of digital
creatures.
We decided to use an acronym that sounds like the word Coral because the
acronym fit
with our desire to create something good for administration but also good for
flexible
research, so we came to Cluster Orchestration and Research Library.  We split
the core
components out into a small concurrent plugin framework called Nucleon, upon
which
CORL is built.  All of our coral sub gems are integrated into these two.
This gem exists only as a installer for people who accidentally spell coral
the right
way when trying to install the CORL system.  Use the CORL gem instead.
== Copyright
Licensed under Apache license, version 2.  See LICENSE.txt for further
details.
Copyright (c) 2013-2014  Adrian Webb <adrian.webb@coralnexus.com>
Coral Technology Group LLC.


%package doc
Summary: Documentation for %{name}
Requires: %{name} = %{version}-%{release}
BuildArch: noarch

%description doc
Documentation for %{name}.

%prep
%setup -q -n %{gem_name}-%{version}

%build
# Create the gem as gem install only works on a gem file
gem build ../%{gem_name}-%{version}.gemspec

# %%gem_install compiles any C extensions and installs the gem into ./%%gem_dir
# by default, so that we can move it into the buildroot in %%install
%gem_install

%install
mkdir -p %{buildroot}%{gem_dir}
cp -a .%{gem_dir}/* \
        %{buildroot}%{gem_dir}/



%check
pushd .%{gem_instdir}
# rspec spec
popd

%files
%dir %{gem_instdir}
%license %{gem_instdir}/LICENSE.txt
%{gem_instdir}/VERSION
%{gem_libdir}
%exclude %{gem_cache}
%{gem_spec}

%files doc
%doc %{gem_docdir}
%doc %{gem_instdir}/.document
%{gem_instdir}/Gemfile
%{gem_instdir}/Gemfile.lock
%doc %{gem_instdir}/README.rdoc
%{gem_instdir}/Rakefile
%{gem_instdir}/coral.gemspec

%changelog
* Mon Apr 18 2022 mockbuilder - 0.5.0-1
- Initial package