summaryrefslogtreecommitdiff
path: root/python-json4json.spec
blob: b14a12f0be6bfd399059b9f48cab7e7a10e043c5 (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
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
%global _empty_manifest_terminate_build 0
Name:		python-JSON4JSON
Version:	0.4.3
Release:	1
Summary:	Configure JSON with JSON
License:	GNU GPLv3
URL:		https://github.com/TrevorBagels/JSON4JSON
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/2d/9f/85ffb35b2b5414c90f6f93a35c8f1bcbfab84ac93f871f3c15641e062af2/JSON4JSON-0.4.3.tar.gz
BuildArch:	noarch


%description
# JSON4JSON
Advanced and easy to use JSON configuration for python. Lets the developer configure their JSON using JSON. That sounds weird, but it's pretty neat and useful for programs that let users customize the settings via JSON. 

**Can be installed via `pip3 install JSON4JSON`**

## Rundown

  JSON4JSON uses a rules file, written by the developer, to transform a configuration file, written by the user, into something easily usable by the developer. 

## Features
  * Unit conversion
  * Variables (in json!)
  * Rules can apply to specific indexes/ranges of arrays
  * Auto generates missing data, can throw errors if you want it to
  * NOT abandoned
## Why does this exist?

  Generally, we want our programs to be capable of customization, so that the user can make the program suit their needs. JSON provides a fairly easy way of doing this; the user can edit their preferences in a JSON file without needing to make changes to the source code. 

  JSON4JSON is JSON, but it makes the life of the developer (and the user), much easier. 
  Sometimes users enter the wrong information into a config file, causing the program to throw errors if it doesn't already check for missing or incorrectly formatted options. All this does is confuse the user, and then they go report it as a bug, when really, they forgot to add something to the config.
  Sometimes developers don't want to tell users exactly how to format certain datatypes, it'd be much easier if something did that automatically. People often argue over the imperial system and the metric system, and users don't like having to convert miles to kilometers. JSON4JSON does all of this automatically, allowing the developer to configure (via `rules.json`) how a config file should be interpreted.




%package -n python3-JSON4JSON
Summary:	Configure JSON with JSON
Provides:	python-JSON4JSON
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-JSON4JSON
# JSON4JSON
Advanced and easy to use JSON configuration for python. Lets the developer configure their JSON using JSON. That sounds weird, but it's pretty neat and useful for programs that let users customize the settings via JSON. 

**Can be installed via `pip3 install JSON4JSON`**

## Rundown

  JSON4JSON uses a rules file, written by the developer, to transform a configuration file, written by the user, into something easily usable by the developer. 

## Features
  * Unit conversion
  * Variables (in json!)
  * Rules can apply to specific indexes/ranges of arrays
  * Auto generates missing data, can throw errors if you want it to
  * NOT abandoned
## Why does this exist?

  Generally, we want our programs to be capable of customization, so that the user can make the program suit their needs. JSON provides a fairly easy way of doing this; the user can edit their preferences in a JSON file without needing to make changes to the source code. 

  JSON4JSON is JSON, but it makes the life of the developer (and the user), much easier. 
  Sometimes users enter the wrong information into a config file, causing the program to throw errors if it doesn't already check for missing or incorrectly formatted options. All this does is confuse the user, and then they go report it as a bug, when really, they forgot to add something to the config.
  Sometimes developers don't want to tell users exactly how to format certain datatypes, it'd be much easier if something did that automatically. People often argue over the imperial system and the metric system, and users don't like having to convert miles to kilometers. JSON4JSON does all of this automatically, allowing the developer to configure (via `rules.json`) how a config file should be interpreted.




%package help
Summary:	Development documents and examples for JSON4JSON
Provides:	python3-JSON4JSON-doc
%description help
# JSON4JSON
Advanced and easy to use JSON configuration for python. Lets the developer configure their JSON using JSON. That sounds weird, but it's pretty neat and useful for programs that let users customize the settings via JSON. 

**Can be installed via `pip3 install JSON4JSON`**

## Rundown

  JSON4JSON uses a rules file, written by the developer, to transform a configuration file, written by the user, into something easily usable by the developer. 

## Features
  * Unit conversion
  * Variables (in json!)
  * Rules can apply to specific indexes/ranges of arrays
  * Auto generates missing data, can throw errors if you want it to
  * NOT abandoned
## Why does this exist?

  Generally, we want our programs to be capable of customization, so that the user can make the program suit their needs. JSON provides a fairly easy way of doing this; the user can edit their preferences in a JSON file without needing to make changes to the source code. 

  JSON4JSON is JSON, but it makes the life of the developer (and the user), much easier. 
  Sometimes users enter the wrong information into a config file, causing the program to throw errors if it doesn't already check for missing or incorrectly formatted options. All this does is confuse the user, and then they go report it as a bug, when really, they forgot to add something to the config.
  Sometimes developers don't want to tell users exactly how to format certain datatypes, it'd be much easier if something did that automatically. People often argue over the imperial system and the metric system, and users don't like having to convert miles to kilometers. JSON4JSON does all of this automatically, allowing the developer to configure (via `rules.json`) how a config file should be interpreted.




%prep
%autosetup -n JSON4JSON-0.4.3

%build
%py3_build

%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .

%files -n python3-JSON4JSON -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 0.4.3-1
- Package Spec generated