On Tue, 2026-08-18 at 16:09 +0000, Sumanth Gavini via lists.openembedded.org 
wrote:
> You are correct, and we should not have different dependencies between 
> packages based on the selected backend.
> 
> In RPM 4, MERGEPERFILEDEPS = 1 resulted in __find_requires %{nil} and
> __find_provides %{nil}, suppressing all autogenerated Requires and Provides.
> 
> In RPM 6, use_internal_dependency_generator is no longer supported for 
> v6-format packages, so the fileattr-based generators always run. The 
> only way I see to suppress dependency generation is to set the 
> individual fileattr macros to %{nil}. We observed incorrectly generated 
> pkgconfig() dependencies on autobuilder and local builds, which led to 
> these changes.
> 
> Should we also suppress all autogenerated Provides in RPM 6 to match the 
> RPM 4 behavior? If so, I'll need to identify the complete list of 
> fileattr-based provides generators that need to be disabled
> 
> Thanks to Alex and Mathieu for their testing and support throughout this 
> upgrade.

Yes, I think we need to disable them.

Before we do that, I would like to understand what information this
changes and whether there are dependencies we're going to miss out
on that we really need to add to do_package.

So there are two things to work out:

- What information do we lose by turning off the rpm 4 rpmdep code in
do_package? Do we need to add/find some of it differently?

- What information do we lose by turning off the RPM 6 autogenerated
dependencies and is there any of that we need to add separately to
do_package somehow?

Cheers,

Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#243694): 
https://lists.openembedded.org/g/openembedded-core/message/243694
Mute This Topic: https://lists.openembedded.org/mt/120783173/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to