diff options
| author | CoprDistGit <infra@openeuler.org> | 2023-04-11 10:58:17 +0000 |
|---|---|---|
| committer | CoprDistGit <infra@openeuler.org> | 2023-04-11 10:58:17 +0000 |
| commit | e7054985adff6760709139128cb4fe0aa6d0ef1c (patch) | |
| tree | d03b8ab22ba998a41b6fd3a02947527a317307c1 | |
| parent | 645752cc7a5d1ef94e36653a5b51f67482e2fbb1 (diff) | |
automatic import of python-configsuite
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-configsuite.spec | 226 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 228 insertions, 0 deletions
@@ -0,0 +1 @@ +/configsuite-0.6.6.tar.gz diff --git a/python-configsuite.spec b/python-configsuite.spec new file mode 100644 index 0000000..01e30c6 --- /dev/null +++ b/python-configsuite.spec @@ -0,0 +1,226 @@ +%global _empty_manifest_terminate_build 0 +Name: python-configsuite +Version: 0.6.6 +Release: 1 +Summary: Config Suite is the result of recognizing the complexity of software configuration. +License: MIT License +URL: https://github.com/equinor/configsuite +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/5c/35/a1fc48be1159433e3a5f3972218f34a2d73d8252ba2ad7f0a32b4168c95a/configsuite-0.6.6.tar.gz +BuildArch: noarch + +Requires: python3-PyYAML + +%description +# Config Suite # + +[](https://circleci.com/gh/equinor/configsuite) +[](https://github.com/features/actions) +[](https://github.com/ambv/black) +[](http://opensource.org/licenses/MIT) +[](https://www.codacy.com/app/markusdregi/configsuite?utm_source=github.com&utm_medium=referral&utm_content=equinor/configsuite&utm_campaign=Badge_Grade) +[](https://www.codacy.com/app/markusdregi/configsuite?utm_source=github.com&utm_medium=referral&utm_content=equinor/configsuite&utm_campaign=Badge_Coverage) +[](https://requires.io/github/equinor/configsuite/requirements/?branch=master) +[](https://configsuite.readthedocs.io/en/latest/?badge=latest) + +## Introduction ## +_Config Suite_ is the result of recognizing the complexity of software configuration, both from a user and developer perspective. And our main goal is to be transparent about this complexity. In particular we aim at providing the user with confirmation when a valid configuration is given, concrete assistance when the configuration is not valid and up-to-date documentation to assist in this work. For a developer we aim at providing a suite that will handle configuration validity with multiple sources of data in a seamless manner, completely remove the burden of special casing and validity checking and automatically generate documentation that is up to date. We also believe that dealing with the complexity of formally verifying a configuration early in development leads to a better design of your configuration. + +## Features ## +- Validate configurations. +- Provide an extensive list of errors when applicable. +- Output a single immutable configuration object where all values are provided. +- Support for multiple data sources, yielding the possibility of default values as well as user and workspace configurations on top of the current configuration. +- Generating documentation that adheres to the technical requirements. +- No exceptions are thrown based on user-input (this is currently not true for validatiors). +- Context based validators and transformations. + +## Documentation ## +Check out the [documentation](https://configsuite.readthedocs.io/en/stable). + +## Future ## +Have a look at the epics and issues in the _GitHub_ [repository](https://github.com/equinor/configsuite/issues). + +## Installation ## +The simplest way to fetch the newest version of _Config Suite_ is via [PyPI](https://pypi.python.org/pypi/configsuite/). + +`pip install configsuite` + +## Developer guidelines ## +Contributions to _Config Suite_ is very much welcome! Bug reports, feature requests and improvements to the documentation or code alike. However, if you are planning a bigger chunk of work or to introduce a concept, initiating a discussion in an issue is encouraged. + +### Running the tests ### +The tests can be executed with `python setup.py test`. Note that the code formatting tests will only be executed with Python `3.6` or higher. + +### Code formatting ### +The entire code base is formatted with [black](https://black.readthedocs.io/en/stable/). + +### Pull request expectations ### +We expect a well-written explanation for smaller PR's and a reference to an issue for larger contributions. In addition, we expect the tests to pass on all commits and the commit messages to be written in imperative style. For more on commit messages read [this](https://chris.beams.io/posts/git-commit/). + +## License ## +_Config Suite_ is licensed under the MIT License. For more information we refer +the reader to the [LICENSE file](https://github.com/equinor/configsuite/blob/master/LICENSE). + + + + +%package -n python3-configsuite +Summary: Config Suite is the result of recognizing the complexity of software configuration. +Provides: python-configsuite +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-configsuite +# Config Suite # + +[](https://circleci.com/gh/equinor/configsuite) +[](https://github.com/features/actions) +[](https://github.com/ambv/black) +[](http://opensource.org/licenses/MIT) +[](https://www.codacy.com/app/markusdregi/configsuite?utm_source=github.com&utm_medium=referral&utm_content=equinor/configsuite&utm_campaign=Badge_Grade) +[](https://www.codacy.com/app/markusdregi/configsuite?utm_source=github.com&utm_medium=referral&utm_content=equinor/configsuite&utm_campaign=Badge_Coverage) +[](https://requires.io/github/equinor/configsuite/requirements/?branch=master) +[](https://configsuite.readthedocs.io/en/latest/?badge=latest) + +## Introduction ## +_Config Suite_ is the result of recognizing the complexity of software configuration, both from a user and developer perspective. And our main goal is to be transparent about this complexity. In particular we aim at providing the user with confirmation when a valid configuration is given, concrete assistance when the configuration is not valid and up-to-date documentation to assist in this work. For a developer we aim at providing a suite that will handle configuration validity with multiple sources of data in a seamless manner, completely remove the burden of special casing and validity checking and automatically generate documentation that is up to date. We also believe that dealing with the complexity of formally verifying a configuration early in development leads to a better design of your configuration. + +## Features ## +- Validate configurations. +- Provide an extensive list of errors when applicable. +- Output a single immutable configuration object where all values are provided. +- Support for multiple data sources, yielding the possibility of default values as well as user and workspace configurations on top of the current configuration. +- Generating documentation that adheres to the technical requirements. +- No exceptions are thrown based on user-input (this is currently not true for validatiors). +- Context based validators and transformations. + +## Documentation ## +Check out the [documentation](https://configsuite.readthedocs.io/en/stable). + +## Future ## +Have a look at the epics and issues in the _GitHub_ [repository](https://github.com/equinor/configsuite/issues). + +## Installation ## +The simplest way to fetch the newest version of _Config Suite_ is via [PyPI](https://pypi.python.org/pypi/configsuite/). + +`pip install configsuite` + +## Developer guidelines ## +Contributions to _Config Suite_ is very much welcome! Bug reports, feature requests and improvements to the documentation or code alike. However, if you are planning a bigger chunk of work or to introduce a concept, initiating a discussion in an issue is encouraged. + +### Running the tests ### +The tests can be executed with `python setup.py test`. Note that the code formatting tests will only be executed with Python `3.6` or higher. + +### Code formatting ### +The entire code base is formatted with [black](https://black.readthedocs.io/en/stable/). + +### Pull request expectations ### +We expect a well-written explanation for smaller PR's and a reference to an issue for larger contributions. In addition, we expect the tests to pass on all commits and the commit messages to be written in imperative style. For more on commit messages read [this](https://chris.beams.io/posts/git-commit/). + +## License ## +_Config Suite_ is licensed under the MIT License. For more information we refer +the reader to the [LICENSE file](https://github.com/equinor/configsuite/blob/master/LICENSE). + + + + +%package help +Summary: Development documents and examples for configsuite +Provides: python3-configsuite-doc +%description help +# Config Suite # + +[](https://circleci.com/gh/equinor/configsuite) +[](https://github.com/features/actions) +[](https://github.com/ambv/black) +[](http://opensource.org/licenses/MIT) +[](https://www.codacy.com/app/markusdregi/configsuite?utm_source=github.com&utm_medium=referral&utm_content=equinor/configsuite&utm_campaign=Badge_Grade) +[](https://www.codacy.com/app/markusdregi/configsuite?utm_source=github.com&utm_medium=referral&utm_content=equinor/configsuite&utm_campaign=Badge_Coverage) +[](https://requires.io/github/equinor/configsuite/requirements/?branch=master) +[](https://configsuite.readthedocs.io/en/latest/?badge=latest) + +## Introduction ## +_Config Suite_ is the result of recognizing the complexity of software configuration, both from a user and developer perspective. And our main goal is to be transparent about this complexity. In particular we aim at providing the user with confirmation when a valid configuration is given, concrete assistance when the configuration is not valid and up-to-date documentation to assist in this work. For a developer we aim at providing a suite that will handle configuration validity with multiple sources of data in a seamless manner, completely remove the burden of special casing and validity checking and automatically generate documentation that is up to date. We also believe that dealing with the complexity of formally verifying a configuration early in development leads to a better design of your configuration. + +## Features ## +- Validate configurations. +- Provide an extensive list of errors when applicable. +- Output a single immutable configuration object where all values are provided. +- Support for multiple data sources, yielding the possibility of default values as well as user and workspace configurations on top of the current configuration. +- Generating documentation that adheres to the technical requirements. +- No exceptions are thrown based on user-input (this is currently not true for validatiors). +- Context based validators and transformations. + +## Documentation ## +Check out the [documentation](https://configsuite.readthedocs.io/en/stable). + +## Future ## +Have a look at the epics and issues in the _GitHub_ [repository](https://github.com/equinor/configsuite/issues). + +## Installation ## +The simplest way to fetch the newest version of _Config Suite_ is via [PyPI](https://pypi.python.org/pypi/configsuite/). + +`pip install configsuite` + +## Developer guidelines ## +Contributions to _Config Suite_ is very much welcome! Bug reports, feature requests and improvements to the documentation or code alike. However, if you are planning a bigger chunk of work or to introduce a concept, initiating a discussion in an issue is encouraged. + +### Running the tests ### +The tests can be executed with `python setup.py test`. Note that the code formatting tests will only be executed with Python `3.6` or higher. + +### Code formatting ### +The entire code base is formatted with [black](https://black.readthedocs.io/en/stable/). + +### Pull request expectations ### +We expect a well-written explanation for smaller PR's and a reference to an issue for larger contributions. In addition, we expect the tests to pass on all commits and the commit messages to be written in imperative style. For more on commit messages read [this](https://chris.beams.io/posts/git-commit/). + +## License ## +_Config Suite_ is licensed under the MIT License. For more information we refer +the reader to the [LICENSE file](https://github.com/equinor/configsuite/blob/master/LICENSE). + + + + +%prep +%autosetup -n configsuite-0.6.6 + +%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-configsuite -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 0.6.6-1 +- Package Spec generated @@ -0,0 +1 @@ +e17a3cd5ce9e0e741780b618029ccc9d configsuite-0.6.6.tar.gz |