blob: 72ddde42b5514c159f3ad6561c84252094bd903c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
%global _empty_manifest_terminate_build 0
%global gem_name scoped_search
Name: rubygem-scoped_search
Version: 4.1.10
Release: 1
Summary: Easily search you ActiveRecord models with a simple query language using a named scope
License: MIT
URL: https://github.com/wvanbergen/scoped_search/wiki
Source0: https://rubygems.org/gems/scoped_search-4.1.10.gem
BuildArch: noarch
Requires: rubygem-activerecord
BuildRequires: ruby
BuildRequires: ruby-devel
BuildRequires: rubygems
BuildRequires: rubygems-devel
BuildRequires: rsync
Provides: rubygem-scoped_search
%description
Scoped search makes it easy to search your ActiveRecord-based models.
It will create a named scope :search_for that can be called with a query string. It will build an SQL query using
the provided query string and a definition that specifies on what fields to search. Because the functionality is
built on named_scope, the result of the search_for call can be used like any other named_scope, so it can be
chained with another scope or combined with will_paginate.
Because it uses standard SQL, it does not require any setup, indexers or daemons. This makes scoped_search
suitable to quickly add basic search functionality to your application with little hassle. On the other hand,
it may not be the best choice if it is going to be used on very large datasets or by a large user base.
%package help
Summary: Development documents and examples for scoped_search
Provides: rubygem-scoped_search-doc
BuildArch: noarch
%description help
Scoped search makes it easy to search your ActiveRecord-based models.
It will create a named scope :search_for that can be called with a query string. It will build an SQL query using
the provided query string and a definition that specifies on what fields to search. Because the functionality is
built on named_scope, the result of the search_for call can be used like any other named_scope, so it can be
chained with another scope or combined with will_paginate.
Because it uses standard SQL, it does not require any setup, indexers or daemons. This makes scoped_search
suitable to quickly add basic search functionality to your application with little hassle. On the other hand,
it may not be the best choice if it is going to be used on very large datasets or by a large user base.
%prep
%autosetup -n scoped_search-4.1.10
gem spec %{SOURCE0} -l --ruby > scoped_search.gemspec
%build
gem build scoped_search.gemspec
%gem_install
%install
mkdir -p %{buildroot}%{gem_dir}
cp -a .%{gem_dir}/* %{buildroot}%{gem_dir}/
rsync -a --exclude=".*" .%{gem_dir}/* %{buildroot}%{gem_dir}/
if [ -d .%{_bindir} ]; then
mkdir -p %{buildroot}%{_bindir}
cp -a .%{_bindir}/* %{buildroot}%{_bindir}/
fi
if [ -d ext ]; then
mkdir -p %{buildroot}%{gem_extdir_mri}/%{gem_name}
if [ -d .%{gem_extdir_mri}/%{gem_name} ]; then
cp -a .%{gem_extdir_mri}/%{gem_name}/*.so %{buildroot}%{gem_extdir_mri}/%{gem_name}
else
cp -a .%{gem_extdir_mri}/*.so %{buildroot}%{gem_extdir_mri}/%{gem_name}
fi
cp -a .%{gem_extdir_mri}/gem.build_complete %{buildroot}%{gem_extdir_mri}/
rm -rf %{buildroot}%{gem_instdir}/ext/
fi
pushd %{buildroot}
touch filelist.lst
if [ -d %{buildroot}%{_bindir} ]; then
find .%{_bindir} -type f -printf "/%h/%f\n" >> filelist.lst
fi
popd
mv %{buildroot}/filelist.lst .
%files -n rubygem-scoped_search -f filelist.lst
%dir %{gem_instdir}
%{gem_instdir}/*
%exclude %{gem_cache}
%{gem_spec}
%files help
%{gem_docdir}/*
%changelog
* Fri Mar 10 2023 Ruby_Bot <Ruby_Bot@openeuler.org>
- Package Spec generated
|
