On Mon, Dec 6, 2021 at 8:09 PM Maxwell G <gotmax@e.email> wrote: > > On Monday, December 6, 2021 6:43:57 PM CST Nico Kadel-Garcia wrote: > > On Mon, Dec 6, 2021 at 3:59 AM Vitaly Zaitsev via devel > > <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > > > On 05/12/2021 04:07, Nico Kadel-Garcia wrote: > > > > This breaks building RPMs for EPEL 8 or Fedora, because the '%doc' and > > > > '%license' macros strip off the subdirectories of the files and > > > > install them directly at the top of the docdir. > > > > > > You should deal with them manually. > > > > > > Example: > > > https://github.com/rpmfusion/tg_owt/blob/master/tg_owt.spec#L124-L161 > > > https://github.com/rpmfusion/tg_owt/blob/master/tg_owt.spec#L178-L179 > > > > Simply put, "no". Manually organizing component names for more than > > 300 README files and more than 100 LICENSE files does not seem a wise > > use of anyone's package compilation time. > > > > If it's necessary, I could see doing something like this instead, or > > using a local macro > > > > cp -D ansible_collections/foo/bar/baz/README.md > > %{buildroot}%{defaultdocdir}/%{package}-%{version}/foo/bbar/baz/README.md > > > > I'll still want to separate '%license" files from "%doc", which means > > I won't just be able to use: > > > > %doc %{defaultdocdir}/%{package}-%{version > > The specfile that Vitaly linked also marks the license files with `%license`. I'm staring at that pull request, which is similar to my tesstable .spec file in various ways. Mind you, in my testing setup, I use: BuildRequires: ansible-core >= 2.11.0 BuildRequires: ansible-core < 2.13.0 Requires: ansible-core >= 2.11.0 Requires: ansible-core < 2.13.0 ansible-5.x works well with ansible-core 2.11, the 2.12 requirement and the related python 3.8 requirement seem to be spurious for the pypo.org published ansible tarball of hundreds of ansible galaxy modules. The suggestion there that those dependencies should be autogenerated does not and will not work because of the mislabeling of the tarball with all the actualy core python modules called "ansible" within the "ansible-core" tarball and RPM, and mislabeling of the moe than 100 ansible_collections python submodules as the new "ansible" tarball. And yes, I'm being a bit harsh about that split and calling it a mislabeling, since it's inconsistent and breaks automated processing. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
