>From a discussion with @Conan-Kudo
> (me) what is the intended purpose behind RPM automatically adding a
> config($pkgname) dependency to both the provides and requires dependency
> lists of a package with a %config declared in the specfile? why self-require
> like that?
> (neal) My understanding is the original intent is to make it trivial to
> identify packages that have config files marked as %config. The self-requires
> thing comes as a consequence of the usage of %config triggering that
> requirement. But honestly, self-requires should be optimized out in general.
> The "other" RPM did this and it nicely reduced the amount of data produced
> for repodata.
I'm curious whether self-requires are something that could be dropped?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2374#discussioncomment-8016524
You are receiving this because you are subscribed to this thread.
Message ID:
<rpm-software-management/rpm/repo-discussions/2374/comments/8016...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
