diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-dotenv-linter.spec | 216 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 218 insertions, 0 deletions
@@ -0,0 +1 @@ +/dotenv-linter-0.4.0.tar.gz diff --git a/python-dotenv-linter.spec b/python-dotenv-linter.spec new file mode 100644 index 0000000..7345607 --- /dev/null +++ b/python-dotenv-linter.spec @@ -0,0 +1,216 @@ +%global _empty_manifest_terminate_build 0 +Name: python-dotenv-linter +Version: 0.4.0 +Release: 1 +Summary: Linting dotenv files like a charm! +License: MIT +URL: https://dotenv-linter.readthedocs.io +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/b1/3a/9073fc1331be389d706ec0bf12a5f42285c7be6ca462e77a6e8cbaff5b8e/dotenv-linter-0.4.0.tar.gz +BuildArch: noarch + +Requires: python3-ply +Requires: python3-click +Requires: python3-click_default_group +Requires: python3-attrs +Requires: python3-typing_extensions +Requires: python3-importlib-metadata + +%description +Simple linter for `.env` files. + +While `.env` files are very simple it is required to keep them consistent. +This tool offers a wide range of consistency rules and best practices. +And it integrates perfectly to any existing workflow. +Read [the announcing post](https://sobolevn.me/2019/01/announcing-dotenv-linter). +## Installation and usage +```bash +pip install dotenv-linter +``` +And then run it: +```bash +dotenv-linter .env .env.template +``` +See [Usage](https://dotenv-linter.readthedocs.io/en/latest/#usage) +section for more information. +## Examples +There are many things that can go wrong in your `.env` files: +```ini +# Next line has leading space which will be removed: + SPACED= +# Equal signs should not be spaced: +KEY = VALUE +# Quotes won't be preserved after parsing, do not use them: +SECRET="my value" +# Beware of duplicate keys! +SECRET=Already defined ;( +# Respect the convention, use `UPPER_CASE`: +kebab-case-name=1 +snake_case_name=2 +``` +And much more! You can find the [full list of violations in our docs](https://dotenv-linter.readthedocs.io/en/latest/pages/violations/). +## Pre-commit hooks +`dotenv-linter` can also be used as a [pre-commit](https://github.com/pre-commit/pre-commit) hook. +To do so, add the following to the `.pre-commit-config.yaml` file at the root of your project: +```yaml +repos: + - repo: https://github.com/wemake-services/dotenv-linter + rev: 0.2.0 # Use the ref you want to point at + hooks: + - id: dotenv-linter +``` +For the more detailed instructions on the pre-commit tool itself, +please refer to [its website](https://pre-commit.com/). +## Gratis +Special thanks goes to [Ignacio Toledo](https://ign.uy) +for creating an awesome logo for the project. + +%package -n python3-dotenv-linter +Summary: Linting dotenv files like a charm! +Provides: python-dotenv-linter +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-dotenv-linter +Simple linter for `.env` files. + +While `.env` files are very simple it is required to keep them consistent. +This tool offers a wide range of consistency rules and best practices. +And it integrates perfectly to any existing workflow. +Read [the announcing post](https://sobolevn.me/2019/01/announcing-dotenv-linter). +## Installation and usage +```bash +pip install dotenv-linter +``` +And then run it: +```bash +dotenv-linter .env .env.template +``` +See [Usage](https://dotenv-linter.readthedocs.io/en/latest/#usage) +section for more information. +## Examples +There are many things that can go wrong in your `.env` files: +```ini +# Next line has leading space which will be removed: + SPACED= +# Equal signs should not be spaced: +KEY = VALUE +# Quotes won't be preserved after parsing, do not use them: +SECRET="my value" +# Beware of duplicate keys! +SECRET=Already defined ;( +# Respect the convention, use `UPPER_CASE`: +kebab-case-name=1 +snake_case_name=2 +``` +And much more! You can find the [full list of violations in our docs](https://dotenv-linter.readthedocs.io/en/latest/pages/violations/). +## Pre-commit hooks +`dotenv-linter` can also be used as a [pre-commit](https://github.com/pre-commit/pre-commit) hook. +To do so, add the following to the `.pre-commit-config.yaml` file at the root of your project: +```yaml +repos: + - repo: https://github.com/wemake-services/dotenv-linter + rev: 0.2.0 # Use the ref you want to point at + hooks: + - id: dotenv-linter +``` +For the more detailed instructions on the pre-commit tool itself, +please refer to [its website](https://pre-commit.com/). +## Gratis +Special thanks goes to [Ignacio Toledo](https://ign.uy) +for creating an awesome logo for the project. + +%package help +Summary: Development documents and examples for dotenv-linter +Provides: python3-dotenv-linter-doc +%description help +Simple linter for `.env` files. + +While `.env` files are very simple it is required to keep them consistent. +This tool offers a wide range of consistency rules and best practices. +And it integrates perfectly to any existing workflow. +Read [the announcing post](https://sobolevn.me/2019/01/announcing-dotenv-linter). +## Installation and usage +```bash +pip install dotenv-linter +``` +And then run it: +```bash +dotenv-linter .env .env.template +``` +See [Usage](https://dotenv-linter.readthedocs.io/en/latest/#usage) +section for more information. +## Examples +There are many things that can go wrong in your `.env` files: +```ini +# Next line has leading space which will be removed: + SPACED= +# Equal signs should not be spaced: +KEY = VALUE +# Quotes won't be preserved after parsing, do not use them: +SECRET="my value" +# Beware of duplicate keys! +SECRET=Already defined ;( +# Respect the convention, use `UPPER_CASE`: +kebab-case-name=1 +snake_case_name=2 +``` +And much more! You can find the [full list of violations in our docs](https://dotenv-linter.readthedocs.io/en/latest/pages/violations/). +## Pre-commit hooks +`dotenv-linter` can also be used as a [pre-commit](https://github.com/pre-commit/pre-commit) hook. +To do so, add the following to the `.pre-commit-config.yaml` file at the root of your project: +```yaml +repos: + - repo: https://github.com/wemake-services/dotenv-linter + rev: 0.2.0 # Use the ref you want to point at + hooks: + - id: dotenv-linter +``` +For the more detailed instructions on the pre-commit tool itself, +please refer to [its website](https://pre-commit.com/). +## Gratis +Special thanks goes to [Ignacio Toledo](https://ign.uy) +for creating an awesome logo for the project. + +%prep +%autosetup -n dotenv-linter-0.4.0 + +%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-dotenv-linter -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.0-1 +- Package Spec generated @@ -0,0 +1 @@ +f78f62f831d98050e5a9e78c6cdf5456 dotenv-linter-0.4.0.tar.gz |