Group :: Development/Ruby
RPM: gem-apipie-rails
Main Changelog Spec Patches Sources Download Gear Bugs and FR Repocop
%define gemname apipie-rails
Name: gem-apipie-rails
Version: 0.8.2
Release: alt1.1
Summary: Ruby on Rails API documentation tool
License: Apache-2.0
Group: Development/Ruby
Url: https://github.com/Apipie/apipie-rails
Vcs: https://github.com/apipie/apipie-rails.git
Packager: Ruby Maintainers Team <ruby at packages.altlinux.org>
BuildArch: noarch
Source: %name-%version.tar
BuildRequires(pre): rpm-build-ruby
%if_with check
BuildRequires: gem(actionpack) >= 5.0
BuildRequires: gem(activesupport) >= 5.0
BuildRequires: gem(rspec-rails) >= 3.0 gem(rspec-rails) < 6
BuildRequires: gem(sqlite3) >= 0
BuildRequires: gem(minitest) >= 0
BuildRequires: gem(maruku) >= 0
BuildRequires: gem(RedCloth) >= 0
BuildRequires: gem(rake) >= 0
BuildRequires: gem(rdoc) >= 0
BuildRequires: gem(simplecov) >= 0
BuildRequires: gem(json-schema) >= 2.8 gem(json-schema) < 3
%endif
%add_findreq_skiplist %ruby_gemslibdir/**/*
%add_findprov_skiplist %ruby_gemslibdir/**/*
%ruby_use_gem_dependency rspec-rails >= 5.0.1,rspec-rails < 6
Requires: gem(actionpack) >= 5.0
Requires: gem(activesupport) >= 5.0
Obsoletes: ruby-apipie-rails < %EVR
Provides: ruby-apipie-rails = %EVR
Provides: gem(apipie-rails) = 0.8.2
%description
Apipie-rails is a DSL and Rails engine for documenting your RESTful API. Instead
of traditional use of #comments, Apipie lets you describe the code, through the
code. This brings advantages like:
* No need to learn yet another syntax, you already know Ruby, right?
* Possibility of reusing the docs for other purposes (such as validation)
* Easier to extend and maintain (no string parsing involved)
* Possibility of reusing other sources for documentation purposes (such as
routes etc.)
The documentation is available from within your app (by default under the
/apipie path.) In development mode, you can see the changes as you go. It's
markup language agnostic, and even provides an API for reusing the documentation
data in JSON.
%package -n gem-apipie-rails-doc
Version: 0.8.2
Release: alt1.1
Summary: Ruby on Rails API documentation tool documentation files
Summary(ru_RU.UTF-8): Файлы сведений для самоцвета apipie-rails
Group: Development/Documentation
BuildArch: noarch
Requires: gem(apipie-rails) = 0.8.2
%description -n gem-apipie-rails-doc
Ruby on Rails API documentation tool documentation files.
Apipie-rails is a DSL and Rails engine for documenting your RESTful API. Instead
of traditional use of #comments, Apipie lets you describe the code, through the
code. This brings advantages like:
* No need to learn yet another syntax, you already know Ruby, right?
* Possibility of reusing the docs for other purposes (such as validation)
* Easier to extend and maintain (no string parsing involved)
* Possibility of reusing other sources for documentation purposes (such as
routes etc.)
The documentation is available from within your app (by default under the
/apipie path.) In development mode, you can see the changes as you go. It's
markup language agnostic, and even provides an API for reusing the documentation
data in JSON.
%description -n gem-apipie-rails-doc -l ru_RU.UTF-8
Файлы сведений для самоцвета apipie-rails.
%package -n gem-apipie-rails-devel
Version: 0.8.2
Release: alt1.1
Summary: Ruby on Rails API documentation tool development package
Summary(ru_RU.UTF-8): Файлы для разработки самоцвета apipie-rails
Group: Development/Ruby
BuildArch: noarch
Requires: gem(apipie-rails) = 0.8.2
Requires: gem(rspec-rails) >= 3.0 gem(rspec-rails) < 6
Requires: gem(sqlite3) >= 0
Requires: gem(minitest) >= 0
Requires: gem(maruku) >= 0
Requires: gem(RedCloth) >= 0
Requires: gem(rake) >= 0
Requires: gem(rdoc) >= 0
Requires: gem(simplecov) >= 0
Requires: gem(json-schema) >= 2.8 gem(json-schema) < 3
%description -n gem-apipie-rails-devel
Ruby on Rails API documentation tool development package.
Apipie-rails is a DSL and Rails engine for documenting your RESTful API. Instead
of traditional use of #comments, Apipie lets you describe the code, through the
code. This brings advantages like:
* No need to learn yet another syntax, you already know Ruby, right?
* Possibility of reusing the docs for other purposes (such as validation)
* Easier to extend and maintain (no string parsing involved)
* Possibility of reusing other sources for documentation purposes (such as
routes etc.)
The documentation is available from within your app (by default under the
/apipie path.) In development mode, you can see the changes as you go. It's
markup language agnostic, and even provides an API for reusing the documentation
data in JSON.
%description -n gem-apipie-rails-devel -l ru_RU.UTF-8
Файлы для разработки самоцвета apipie-rails.
%prep
%setup
%build
%ruby_build
%install
%ruby_install
%check
%ruby_test
%files
%doc README.rst lib/generators/apipie/install/README rel-eng/packages/.readme
%ruby_gemspec
%ruby_gemlibdir
%files -n gem-apipie-rails-doc
%doc README.rst lib/generators/apipie/install/README rel-eng/packages/.readme
%ruby_gemdocdir
%files -n gem-apipie-rails-devel
%doc README.rst lib/generators/apipie/install/README rel-eng/packages/.readme
%changelog
…
Full changelog you can see here
Name: gem-apipie-rails
Version: 0.8.2
Release: alt1.1
Summary: Ruby on Rails API documentation tool
License: Apache-2.0
Group: Development/Ruby
Url: https://github.com/Apipie/apipie-rails
Vcs: https://github.com/apipie/apipie-rails.git
Packager: Ruby Maintainers Team <ruby at packages.altlinux.org>
BuildArch: noarch
Source: %name-%version.tar
BuildRequires(pre): rpm-build-ruby
%if_with check
BuildRequires: gem(actionpack) >= 5.0
BuildRequires: gem(activesupport) >= 5.0
BuildRequires: gem(rspec-rails) >= 3.0 gem(rspec-rails) < 6
BuildRequires: gem(sqlite3) >= 0
BuildRequires: gem(minitest) >= 0
BuildRequires: gem(maruku) >= 0
BuildRequires: gem(RedCloth) >= 0
BuildRequires: gem(rake) >= 0
BuildRequires: gem(rdoc) >= 0
BuildRequires: gem(simplecov) >= 0
BuildRequires: gem(json-schema) >= 2.8 gem(json-schema) < 3
%endif
%add_findreq_skiplist %ruby_gemslibdir/**/*
%add_findprov_skiplist %ruby_gemslibdir/**/*
%ruby_use_gem_dependency rspec-rails >= 5.0.1,rspec-rails < 6
Requires: gem(actionpack) >= 5.0
Requires: gem(activesupport) >= 5.0
Obsoletes: ruby-apipie-rails < %EVR
Provides: ruby-apipie-rails = %EVR
Provides: gem(apipie-rails) = 0.8.2
%description
Apipie-rails is a DSL and Rails engine for documenting your RESTful API. Instead
of traditional use of #comments, Apipie lets you describe the code, through the
code. This brings advantages like:
* No need to learn yet another syntax, you already know Ruby, right?
* Possibility of reusing the docs for other purposes (such as validation)
* Easier to extend and maintain (no string parsing involved)
* Possibility of reusing other sources for documentation purposes (such as
routes etc.)
The documentation is available from within your app (by default under the
/apipie path.) In development mode, you can see the changes as you go. It's
markup language agnostic, and even provides an API for reusing the documentation
data in JSON.
%package -n gem-apipie-rails-doc
Version: 0.8.2
Release: alt1.1
Summary: Ruby on Rails API documentation tool documentation files
Summary(ru_RU.UTF-8): Файлы сведений для самоцвета apipie-rails
Group: Development/Documentation
BuildArch: noarch
Requires: gem(apipie-rails) = 0.8.2
%description -n gem-apipie-rails-doc
Ruby on Rails API documentation tool documentation files.
Apipie-rails is a DSL and Rails engine for documenting your RESTful API. Instead
of traditional use of #comments, Apipie lets you describe the code, through the
code. This brings advantages like:
* No need to learn yet another syntax, you already know Ruby, right?
* Possibility of reusing the docs for other purposes (such as validation)
* Easier to extend and maintain (no string parsing involved)
* Possibility of reusing other sources for documentation purposes (such as
routes etc.)
The documentation is available from within your app (by default under the
/apipie path.) In development mode, you can see the changes as you go. It's
markup language agnostic, and even provides an API for reusing the documentation
data in JSON.
%description -n gem-apipie-rails-doc -l ru_RU.UTF-8
Файлы сведений для самоцвета apipie-rails.
%package -n gem-apipie-rails-devel
Version: 0.8.2
Release: alt1.1
Summary: Ruby on Rails API documentation tool development package
Summary(ru_RU.UTF-8): Файлы для разработки самоцвета apipie-rails
Group: Development/Ruby
BuildArch: noarch
Requires: gem(apipie-rails) = 0.8.2
Requires: gem(rspec-rails) >= 3.0 gem(rspec-rails) < 6
Requires: gem(sqlite3) >= 0
Requires: gem(minitest) >= 0
Requires: gem(maruku) >= 0
Requires: gem(RedCloth) >= 0
Requires: gem(rake) >= 0
Requires: gem(rdoc) >= 0
Requires: gem(simplecov) >= 0
Requires: gem(json-schema) >= 2.8 gem(json-schema) < 3
%description -n gem-apipie-rails-devel
Ruby on Rails API documentation tool development package.
Apipie-rails is a DSL and Rails engine for documenting your RESTful API. Instead
of traditional use of #comments, Apipie lets you describe the code, through the
code. This brings advantages like:
* No need to learn yet another syntax, you already know Ruby, right?
* Possibility of reusing the docs for other purposes (such as validation)
* Easier to extend and maintain (no string parsing involved)
* Possibility of reusing other sources for documentation purposes (such as
routes etc.)
The documentation is available from within your app (by default under the
/apipie path.) In development mode, you can see the changes as you go. It's
markup language agnostic, and even provides an API for reusing the documentation
data in JSON.
%description -n gem-apipie-rails-devel -l ru_RU.UTF-8
Файлы для разработки самоцвета apipie-rails.
%prep
%setup
%build
%ruby_build
%install
%ruby_install
%check
%ruby_test
%files
%doc README.rst lib/generators/apipie/install/README rel-eng/packages/.readme
%ruby_gemspec
%ruby_gemlibdir
%files -n gem-apipie-rails-doc
%doc README.rst lib/generators/apipie/install/README rel-eng/packages/.readme
%ruby_gemdocdir
%files -n gem-apipie-rails-devel
%doc README.rst lib/generators/apipie/install/README rel-eng/packages/.readme
%changelog
…
Full changelog you can see here