Replies: 2 comments
-
You should ask the original package developers to do that. You can also add it to the conda-forge build process as a patch like what debian does https://sources.debian.org/patches/udunits/2.2.28-5/pkg-config.patch, but sending it upstream is preferred. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks. Sent an email to suppport-udunits@unidata.ucar.edu. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a question: should a missing
*.pc
file be added inside conda-forge build process, or the bug report passed upstream to the original package developers? The package in question is udunits2. I had trouble building my python extension and asked for help on the Python discourse forum: https://discuss.python.org/t/meson-python-and-conda-am-i-doing-it-right/26705.For example, zlib provides the file
zlib.pc
. The udunits source from unidata does not. However, Debian's maintainers addudunits.pc
to libudunits2-dev: https://packages.debian.org/sid/armhf/libudunits2-dev/filelist.I am new to this forum, though I have been using conda-forge as a source for python packages for a few years. I thought I better ask before making a PR.
Beta Was this translation helpful? Give feedback.
All reactions