Arch Linux

Can you please clarify what is the bug or the problem that needs a fix? Please provide a way to reproduce it.

Are you aware that when using PYBIND11_GLOBAL_SDIST the python files becomes missing?

I've dived deeper in pybind11 documentation and find an author explanation on why the split into [wheel/sdist](https://github.com/pybind/pybind11/pull/2588) was introduced and [how to use properly build the pybind11](https://github.com/pybind/pybind11/blob/e37921d7617f7bf87ee2fa9591c9cec91ae216b4/.github/CONTRIBUTING.md#explanation-of-the-sdistwheel-building-design).

I'm aware of the differences of the available installation procedures (with and without PYBIND11_GLOBAL_SDIST). And I've already talked to the responsible upstream developer about this for further clarification.

As I already said, when using PYBIND11_GLOBAL_SDIST the python files becomes missing. As a consequence, the users will lose the functionality of doing an 'import pybind11' in python. Our Arch package installs the python files, so does Debian, and so does Fedora. I think we can maintain these python files on our Arch package, as they don't hurt and makes the package to be more complete.

As far I understand, python software expects their target files to be installed inside the python's site-packages directory, even if they are C++ headers, cmake files or any other file. If you take a look at other repository packages that have python software, you'll see that many of them install all sort of files inside python's site-packages directory, like .h/.xml/.html/.js/.png/.gif/.so/whatever files. As some examples I can cite scons, deluge, python-numpy, python-matplotlib, python-twisted and python-wxpython. You can also see that Debian and Fedora install the C++ headers and cmake files inside python's site-package directory in their corresponding pybind11 package. So, I see no need to be concerned about the C++ headers and cmake files being installed inside the python's site-packages directory, because this is expected and is also by upstream design.

That being said, I still cannot see what is the bug or the problem that needs a fix. (and you did not answered my question)

Ok, I see where I was wrong. Packaging with PYBIND11_GLOBAL_SDIST works but only for `cmake` packages (like aur/mitsuba2-git), but if package leverages `PEP518` build system (extra/python-build) it requires the `pybind11` python module that is discarded in sdist version of `pybind11`.

Thanks for explanation and sorry for my incomprehension of the subject :)

btw. I've also take a looksies at how other distros is packaging `pybind11` and found this script from `alpine-linux`: https://git.alpinelinux.org/aports/tree/community/py3-pybind11/APKBUILD
Can't tell if it follows jwenzel intention as it weirdly splits files into base/dev packages.

No problem. You're welcome.

Closing as requested by the OP.