> Dnia 18 maj 2017 o 23:19 Reindl Harald <h.reindl@xxxxxxxxxxxxx> napisał(a): > > > > > Am 18.05.2017 um 23:13 schrieb Rafal Luzynski: > > On 18 May 2017 at 11:03, Nico Kadel-Garcia <nkadel@xxxxxxxxx> wrote: > >> It's not just packages with explicitly published dependencies. It's a > >> lot of configuration tools with implicit dependencies, whose authors > >> didn't imagine at the time of authorship that basic utilities like > >> "/sbin/ifconfig". These tools may be entirely local and outside of > >> RPM's, or may never have bothered to declare what they thought was an > >> implicit provision as part of running on an RPM based Linux. For > >> example, I note on the older systems I have immediate access to that > >> ifconfig is used in the python "virtinst" and "uuid" modules. > > > > If there are implicit dependencies what about converting them to > > explicit so they will be easier to find in future? > > a) how do you find them I will not. :-) One can only ask the packagers to add these dependencies explicitly if they know they are implicit or one can spot accidentally. Somehow Nico discovered that virtinst and uuid use ifconfig. Unfortunately, I have no good and reliable way to find all dependencies. > b) you can't cover "These tools may be entirely local" anyways That's true for any dependency. > c) net-tools is just fine and as long as iproute can't > provide 100% backward behavior it's unacceptable as replacement > > sysadmins don't give a damn waht a replacement can do additionally - the > first step to replace something is *behave identical* and after that > consider enhancements - period It's been agreed that the aim is not to remove net-tools, at least not in a predictable future. Adding explicit dependencies should not change anything except making it easier to find them in future. Regards, Rafal _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
