Re: inject rpm dependency depending on library symbol?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 9 February 2018 at 15:33, Rex Dieter <rdieter@xxxxxxxxxxxx> wrote:
I'm exploring possibilities on how to track usage of a particular library
symbol via rpm dependencies.

In particular, whenever a package is built that includes a dependency on
library symbol:
libQt5Core.so.5(Qt_5_PRIVATE_API)

I'd like to inject additional dependencies, something like:
Requires: qt5-qtbase = %{_qt5_version}

I've been told debian does a variant of this, but I've not been able to come
up with any good way to do that here.  Any ideas or suggestions?

You know it is some old joke about colonist and locals in North America.
It was late autumn and one of the colonist spotted some local guy collecting sticks. He was born in the city so he never saw someone collecting sticks.
When he back to the colony he was so excited that he told what he saw to his friends. They started scratching own heads and after discussion colonist come to the conclusions that probably locals knows that winter will be harsh so they need to spend more time to collect more heavy logs to survive coming winter.
When locals spotted this they organized local tribe elders meeting to discuss what colonist are doing. Because they knew colonists only few months and they've already saw many amazing things they come to the conclusion that colonist probably somehow knows that this winter will be harsh so they decided to spend more time to collect more wood before coming winter as well.

Doing something only because someone is doing something without understanding why it is done is really bad way.
Try to add to this picture that current SONAME dependency generator currently used for more then decade with only small cleanups.
So far no one found any issue with current generator so please do not waste your time implement something to mimic something.

Engineering is not about assuming something and you just assumed that this type of additional dependencies is fixing some unknown problem,
Do not try to fix *possible* problems but only those *already known* as well (and list of those problems is reaaaly long).
If you want still dig around this hole just try to talk with Debian guys and ask then why they are doing this.

kloczek
-- 
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux