Please branch and build adobe-mappings-cmap in epel10. If you do not wish to maintain adobe-mappings-cmap in epel10, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package (FAS: music); please add me through https://src.fedoraproject.org/rpms/adobe-mappings-cmap/adduser
This isn’t a very high priority, but I would like to offer python-pdfminer in EPEL10, and having adobe-mappings-cmap in EPEL10 would make that possible. (The only other missing dependency is python-setuptools-git-versioning, which I can handle as a co-maintainer.)
Hi Ben, adobe-mappings-cmap is present in Centos Stream 10 (in AppStream repo), so I can't create epel10 version for it - AFAIK the components which are in Centos Stream cannot be in EPEL. I've checked python-pdfminer SPEC file about what exactly do you need adobe-mappings-cmap - it looks you need its devel subpackage for building, which contains only this file /usr/lib/rpm/macros.d/macros.adobe-mappings-cmap with this macro definition: %adobe_mappings_rootpath /usr/share/adobe/resources/mapping/ I could move the rpm into CRB repository, so you could build python-pdfminer, but to be honest, given the fact it is only one macro, adobe-mappings-cmap has not changed in the previous Centos versions and python-pdfminer is the first package to request it, I would say it would make more sense to define/hardcode the path in python-pdfminer for EPEL, rather than bringing adobe-mappings-cmap-devel into CRB repository. If that does not work for you and you would like adobe-mappings-cmap-devel to be available in Centos Stream, do file an issue for project RHEL and component adobe-mappings-cmap at https://issues.redhat.com . Thank you and have a nice day! Zdenek
Thanks for the quick and helpful response! I guess it’s been a while since I last encountered a buildroot-only -devel package; I should have checked https://tiny.distro.builders/view-packages--view-c10s.html first, but for some reason it didn’t occur to me. You’re correct that hard-coding the value of the adobe_mappings_rootpath is an easy, sensible, and effective workaround.