Because Fedora is a self-hosted system, circular dependencies are a fact of life. Self-hosted compilers and the like will always exist.
But I think the circular BR nature of redhat-rpm-config and macro packages is unnecessary self-inflicted pain. Currently, I am trying to backport (into a downstream distribution) the introduction of go-srpm-macros into redhat-rpm-config: http://pkgs.fedoraproject.org/cgit/redhat-rpm-config.git/commit/?id=ba49b893751cd036905b642bc671814301cd2edb Yet because redhat-rpm-config itself is pulled into the build root for go-srpm-macros, it introduces a circular build dependency. I could imagine external ways out of this (try dropping the BR of rrc for go-srpm-macros externally), but it would seem to me to be a lot saner just to include the macros themselves in redhat-rpm-config. Thoughts? (Is this the right list?) -- buildsys mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/buildsys
