diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-ldfparser.spec | 138 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 140 insertions, 0 deletions
@@ -0,0 +1 @@ +/ldfparser-0.19.0.tar.gz diff --git a/python-ldfparser.spec b/python-ldfparser.spec new file mode 100644 index 0000000..53e234b --- /dev/null +++ b/python-ldfparser.spec @@ -0,0 +1,138 @@ +%global _empty_manifest_terminate_build 0 +Name: python-ldfparser +Version: 0.19.0 +Release: 1 +Summary: LDF Language support for Python +License: MIT +URL: https://github.com/c4deszes/ldfparser +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/a0/79/697c09330a98cb5f8630d8f564497aad35a2ac795ea441e9b8dd113f1f3a/ldfparser-0.19.0.tar.gz +BuildArch: noarch + +Requires: python3-lark +Requires: python3-bitstruct +Requires: python3-jinja2 +Requires: python3-setuptools +Requires: python3-wheel +Requires: python3-twine +Requires: python3-pytest +Requires: python3-pytest-cov +Requires: python3-pytest-benchmark +Requires: python3-jsonschema +Requires: python3-pylint +Requires: python3-flake8 + +%description +## Disclaimers +The library is still in a pre-release state, therefore features may break between minor versions. +For this reason it's recommended that productive environments pin to the exact version of the +library and do an integration test or review when updating the version. Breaking changes and how to +migrate to the new version will be documented in the +[changelog](https://github.com/c4deszes/ldfparser/blob/master/CHANGELOG.md) and on the +[Github releases page](https://github.com/c4deszes/ldfparser/releases). +The tool has been written according the LIN standards [1.3](docs/external/LIN_1.3.pdf), +[2.0](docs/external/LIN_2.0.pdf), [2.1](docs/external/LIN_2.1.pdf) and [2.2A](docs/external/LIN_2.2A.pdf), +but due to errors in the documentation there's no guarantee that the library will be able to parse your LDF. +In such cases if possible first verify the LDF with a commercial tool such as Vector LDF Explorer or the +tool that was used to create the LDF. If the LDF seems to be correct then open a new issue. +I also recommend trying the LDF to JSON conversion mechanism, see if that succeeds. +The LIN standard is now known as [ISO 17987](https://www.iso.org/standard/61222.html) which +clears up some of the confusing parts in the 2.2A specification. Since this new standard is not +freely available **this library won't support the modifications present in ISO 17987**. I don't +think it's going to a huge problem because the LIN 2.2A released in 2010 has overall better adoption. +The LDF usually contains sensitive information, if you need to open an issue related to the parser +then try to provide either an anonymized version with signals and frames obfuscated or just the + +%package -n python3-ldfparser +Summary: LDF Language support for Python +Provides: python-ldfparser +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-ldfparser +## Disclaimers +The library is still in a pre-release state, therefore features may break between minor versions. +For this reason it's recommended that productive environments pin to the exact version of the +library and do an integration test or review when updating the version. Breaking changes and how to +migrate to the new version will be documented in the +[changelog](https://github.com/c4deszes/ldfparser/blob/master/CHANGELOG.md) and on the +[Github releases page](https://github.com/c4deszes/ldfparser/releases). +The tool has been written according the LIN standards [1.3](docs/external/LIN_1.3.pdf), +[2.0](docs/external/LIN_2.0.pdf), [2.1](docs/external/LIN_2.1.pdf) and [2.2A](docs/external/LIN_2.2A.pdf), +but due to errors in the documentation there's no guarantee that the library will be able to parse your LDF. +In such cases if possible first verify the LDF with a commercial tool such as Vector LDF Explorer or the +tool that was used to create the LDF. If the LDF seems to be correct then open a new issue. +I also recommend trying the LDF to JSON conversion mechanism, see if that succeeds. +The LIN standard is now known as [ISO 17987](https://www.iso.org/standard/61222.html) which +clears up some of the confusing parts in the 2.2A specification. Since this new standard is not +freely available **this library won't support the modifications present in ISO 17987**. I don't +think it's going to a huge problem because the LIN 2.2A released in 2010 has overall better adoption. +The LDF usually contains sensitive information, if you need to open an issue related to the parser +then try to provide either an anonymized version with signals and frames obfuscated or just the + +%package help +Summary: Development documents and examples for ldfparser +Provides: python3-ldfparser-doc +%description help +## Disclaimers +The library is still in a pre-release state, therefore features may break between minor versions. +For this reason it's recommended that productive environments pin to the exact version of the +library and do an integration test or review when updating the version. Breaking changes and how to +migrate to the new version will be documented in the +[changelog](https://github.com/c4deszes/ldfparser/blob/master/CHANGELOG.md) and on the +[Github releases page](https://github.com/c4deszes/ldfparser/releases). +The tool has been written according the LIN standards [1.3](docs/external/LIN_1.3.pdf), +[2.0](docs/external/LIN_2.0.pdf), [2.1](docs/external/LIN_2.1.pdf) and [2.2A](docs/external/LIN_2.2A.pdf), +but due to errors in the documentation there's no guarantee that the library will be able to parse your LDF. +In such cases if possible first verify the LDF with a commercial tool such as Vector LDF Explorer or the +tool that was used to create the LDF. If the LDF seems to be correct then open a new issue. +I also recommend trying the LDF to JSON conversion mechanism, see if that succeeds. +The LIN standard is now known as [ISO 17987](https://www.iso.org/standard/61222.html) which +clears up some of the confusing parts in the 2.2A specification. Since this new standard is not +freely available **this library won't support the modifications present in ISO 17987**. I don't +think it's going to a huge problem because the LIN 2.2A released in 2010 has overall better adoption. +The LDF usually contains sensitive information, if you need to open an issue related to the parser +then try to provide either an anonymized version with signals and frames obfuscated or just the + +%prep +%autosetup -n ldfparser-0.19.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-ldfparser -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Wed May 31 2023 Python_Bot <Python_Bot@openeuler.org> - 0.19.0-1 +- Package Spec generated @@ -0,0 +1 @@ +1366386cc170bed3322fbdce0b47f55b ldfparser-0.19.0.tar.gz |