You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vast majority of packages out there have at least one sub-package, and most of them want to ensure the sub-packages stay in sync with the main package, simply to avoid having to test and/or support packages with arbitrary theoretically legitimate combinations which can lead to time-consuming corner-case bugs. So on top of all the automatically generated soname dependencies and such, we have specs full of constructs like this to force it:
Requires: %{name}%{?_isa} = %{version}-%{release}
This is ugly and error-prone boilerplate in specs, and sometimes creates artificial dependency loops that mess up with ordering. And so on. Rpm should automate this somehow, and that somehow should not include littering packages with umphteen more dependencies automatically, but something more intelligent.
The text was updated successfully, but these errors were encountered:
The vast majority of packages out there have at least one sub-package, and most of them want to ensure the sub-packages stay in sync with the main package, simply to avoid having to test and/or support packages with arbitrary theoretically legitimate combinations which can lead to time-consuming corner-case bugs. So on top of all the automatically generated soname dependencies and such, we have specs full of constructs like this to force it:
This is ugly and error-prone boilerplate in specs, and sometimes creates artificial dependency loops that mess up with ordering. And so on. Rpm should automate this somehow, and that somehow should not include littering packages with umphteen more dependencies automatically, but something more intelligent.
The text was updated successfully, but these errors were encountered: