%global _empty_manifest_terminate_build 0 Name: python-dazel Version: 0.0.41 Release: 1 Summary: Run bazel in Docker, in a reproducible and portable container. License: MIT URL: https://github.com/nadirizr/dazel Source0: https://mirrors.aliyun.com/pypi/web/packages/60/57/030f0ed070561eb22a997e2a17cc0f0e48497f280ad3325c52e6a4b5cb47/dazel-0.0.41.tar.gz BuildArch: noarch Requires: python3-check-manifest Requires: python3-coverage %description Run Google's bazel inside a docker container via a seamless proxy. bazel is awesome at creating fast and reproducible builds on your own development environment. The problem is that it works in an imperfect and non-portable environment. Enter dazel. dazel allows you to create your build environment as a Docker image, either via a Dockerfile or a prebuilt repository. The tool itself is a simple python script that sends the command line arguments directly to bazel inside the container, and maps all of the necessary volumes to make it seamless to you. It uses the 'docker exec' command to achieve this, and maps the current directory and the bazel-WORKDIR link directory so that the results appear on the host as if you ran the command locally on the host. It is run the same way you would bazel: dazel build //my/cool/package/... dazel run //my/cool/package:target This was a simple build and run. The command line arguments were sent as-is into the docker container, and the output was run in the same manner inside the container. Running the command for the first time will start the container on it's own, and it will automatically detect if there is need to rebuild or restart the container (if the Dockerfile is newer than the conatiner). You can configure anything you need through the ".dazelrc" file in the same directory. Take a look at the configuration section for information on how to write one. %package -n python3-dazel Summary: Run bazel in Docker, in a reproducible and portable container. Provides: python-dazel BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-dazel Run Google's bazel inside a docker container via a seamless proxy. bazel is awesome at creating fast and reproducible builds on your own development environment. The problem is that it works in an imperfect and non-portable environment. Enter dazel. dazel allows you to create your build environment as a Docker image, either via a Dockerfile or a prebuilt repository. The tool itself is a simple python script that sends the command line arguments directly to bazel inside the container, and maps all of the necessary volumes to make it seamless to you. It uses the 'docker exec' command to achieve this, and maps the current directory and the bazel-WORKDIR link directory so that the results appear on the host as if you ran the command locally on the host. It is run the same way you would bazel: dazel build //my/cool/package/... dazel run //my/cool/package:target This was a simple build and run. The command line arguments were sent as-is into the docker container, and the output was run in the same manner inside the container. Running the command for the first time will start the container on it's own, and it will automatically detect if there is need to rebuild or restart the container (if the Dockerfile is newer than the conatiner). You can configure anything you need through the ".dazelrc" file in the same directory. Take a look at the configuration section for information on how to write one. %package help Summary: Development documents and examples for dazel Provides: python3-dazel-doc %description help Run Google's bazel inside a docker container via a seamless proxy. bazel is awesome at creating fast and reproducible builds on your own development environment. The problem is that it works in an imperfect and non-portable environment. Enter dazel. dazel allows you to create your build environment as a Docker image, either via a Dockerfile or a prebuilt repository. The tool itself is a simple python script that sends the command line arguments directly to bazel inside the container, and maps all of the necessary volumes to make it seamless to you. It uses the 'docker exec' command to achieve this, and maps the current directory and the bazel-WORKDIR link directory so that the results appear on the host as if you ran the command locally on the host. It is run the same way you would bazel: dazel build //my/cool/package/... dazel run //my/cool/package:target This was a simple build and run. The command line arguments were sent as-is into the docker container, and the output was run in the same manner inside the container. Running the command for the first time will start the container on it's own, and it will automatically detect if there is need to rebuild or restart the container (if the Dockerfile is newer than the conatiner). You can configure anything you need through the ".dazelrc" file in the same directory. Take a look at the configuration section for information on how to write one. %prep %autosetup -n dazel-0.0.41 %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-dazel -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri Jun 09 2023 Python_Bot - 0.0.41-1 - Package Spec generated