So is it any final decision about start use by default --as-needed in linker options? Looking again on whole discussion across this thread and on https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/3 I don't see any arguments against start use --as-needed by default so looks like only reason why such change still is not introduced is more physiological than technical as such change will affect majority of the packages in Fedora. bringing as result HUGE reduction of the SONAME dependencies but at the same time still it may unhide some non empty set of cases when still it will be necessary to apply some minor fixes. In my opinion number of affected packages will be very low (few). BTW looks like similar situation like with --as-needed is with move execution ldconfig from each package caring libraries to glibc file trigger. Ticket https://bugzilla.redhat.com/show_bug.cgi?id=1380878 which has been opened more than year ago still has no go/no go decision and no one is able to cast even single technical stone against such change. As same as in case of use --as-neded most of the distribution packages will be affected however in case of the ldconfig file trigger introduction in the glibc it will change initially nothing so risk here is even lower than in case of --as-needed (despite fact that even here such risk is veeeery low). Simple introduction of the ldconfig file trigger will unlock possibility to start developers remove %post/%postub ldconfig execution one by one. As f28 development cycle still is in the middle IMO it is right time to apply at least one of those two changes (if not both). kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
