Hi all, I'm wondering why /usr/bin/pkg-config seems to be forced into :devel by: '%(bindir)s/..*-config' in /etc/conary/components/base/devel.py
I understand /usr/bin/*-config is usually only required for development. But what would you expect when you install :runtime of a development tool? I've searched for some /usr/bin/*-config files and had a look at the corresponding :runtime of that package. freetype:runtime (ftlint might be a developer tool?) SDL:runtime contains a /etc/profile.d hack pkgconfig:runtime doesn't exist libxml2:runtime doesn't exist curl:runtime OK (not a developer tool) wxWidgets:runtime doesn't exist llvm:runtime: a lot of development tools ;-) gd:runtime OK (not a developer tool) python:runtime hmm not sure about pydoc IMHO it would be better to introduce a new component name: develruntime to contain all development executable tools from gcc to pkg-config. Or (might be easier), move all development tools from a non development package (like curl, gd and python) to another package name (curl- devel:runtime, gd-devel:runtime, python-devel:runtime) Oh, I bumped into this with the development of condora (Fedora build using Conary). I need to translate pkgconfig to pkgconfig:devel but gcc to gcc:runtime for building the RPM. Please let me know what you think! Dick (aka meeuw) _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
