%global _empty_manifest_terminate_build 0 Name: python-conda-merge Version: 0.2.0 Release: 1 Summary: Tool for merging conda environment files License: MIT URL: https://github.com/amitbeka/conda-merge Source0: https://mirrors.nju.edu.cn/pypi/web/packages/5e/32/2b1ebac466924462478fb69cd92e4de1e471f599cd25c6180d08f64452dc/conda-merge-0.2.0.tar.gz BuildArch: noarch %description Tool for merging Conda (Anaconda) environment files into one file. This is used to merge your application environment file with any other environment file you might need (e.g. unit-tests, debugging, jupyter notebooks) and create a consistent environment without breaking dependencies from the previous environment files. **Installation**: pip install conda-merge **Usage**: conda-merge FILE1 FILE2 ... FILE-N > OUTPUT-FILE A common problem with multiple environment files is that of pinned dependencies: let's say ``environment.yml`` contains the dependency ``numpy=1.7``, and your ``dev-environment.yml`` contains ``pandas`` as a dependency. If you sequentially apply the environment files (``conda env update -f environment.yml`` and then ``conda env update -f dev-environment.yml``) ``numpy`` will no longer be pinned and will be upgraded to the latest version. One option to solve it is by using the pinned dependencies file in the environment directory, but this means storing your dependencies in another file which interacts with ``environment.yml``, and makes the dependencies less clear to other users. This script enables you to merge the two environment files and then run only one ``conda env`` command to apply the change. %package -n python3-conda-merge Summary: Tool for merging conda environment files Provides: python-conda-merge BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-conda-merge Tool for merging Conda (Anaconda) environment files into one file. This is used to merge your application environment file with any other environment file you might need (e.g. unit-tests, debugging, jupyter notebooks) and create a consistent environment without breaking dependencies from the previous environment files. **Installation**: pip install conda-merge **Usage**: conda-merge FILE1 FILE2 ... FILE-N > OUTPUT-FILE A common problem with multiple environment files is that of pinned dependencies: let's say ``environment.yml`` contains the dependency ``numpy=1.7``, and your ``dev-environment.yml`` contains ``pandas`` as a dependency. If you sequentially apply the environment files (``conda env update -f environment.yml`` and then ``conda env update -f dev-environment.yml``) ``numpy`` will no longer be pinned and will be upgraded to the latest version. One option to solve it is by using the pinned dependencies file in the environment directory, but this means storing your dependencies in another file which interacts with ``environment.yml``, and makes the dependencies less clear to other users. This script enables you to merge the two environment files and then run only one ``conda env`` command to apply the change. %package help Summary: Development documents and examples for conda-merge Provides: python3-conda-merge-doc %description help Tool for merging Conda (Anaconda) environment files into one file. This is used to merge your application environment file with any other environment file you might need (e.g. unit-tests, debugging, jupyter notebooks) and create a consistent environment without breaking dependencies from the previous environment files. **Installation**: pip install conda-merge **Usage**: conda-merge FILE1 FILE2 ... FILE-N > OUTPUT-FILE A common problem with multiple environment files is that of pinned dependencies: let's say ``environment.yml`` contains the dependency ``numpy=1.7``, and your ``dev-environment.yml`` contains ``pandas`` as a dependency. If you sequentially apply the environment files (``conda env update -f environment.yml`` and then ``conda env update -f dev-environment.yml``) ``numpy`` will no longer be pinned and will be upgraded to the latest version. One option to solve it is by using the pinned dependencies file in the environment directory, but this means storing your dependencies in another file which interacts with ``environment.yml``, and makes the dependencies less clear to other users. This script enables you to merge the two environment files and then run only one ``conda env`` command to apply the change. %prep %autosetup -n conda-merge-0.2.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-conda-merge -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri May 05 2023 Python_Bot - 0.2.0-1 - Package Spec generated