[Not defending the rather odd NMU practice here, but ...] On Fri, Oct 25, 2013 at 12:57:24PM +0200, Rene Engelhard wrote: > Until then there's no action needed to make it work in Debian. Debian is > not Ubuntus development platform, so why should one NMU stuff for this > when it's not needed in Debian _yet_?
The usefulness of supporting --as-needed isn't because of Ubuntu. It's because switching --as-needed on across the board lets us easily cut out a swathe of unnecessary direct DT_NEEDED entries in binaries, which in turn removes unnecessary direct dependencies which cause transition headache, and reduces the probability of future crashes due to libraries that are both directly and indirectly linked changing their SONAME without perfect coordination. Forget about Ubuntu, and the unsurprising fact that a good percentage of the patches you see for this class of issue come from Ubuntu; this would be good for *Debian*. By saying "it's not needed in Debian yet", you're setting up a deadlock. The more packages that would fail to build as a consequence, the harder it is to change the toolchain defaults. It's valuable to fix this kind of thing in advance, just as (for example) it's valuable to make sure that config.guess/sub files are suitably updated in advance of somebody actually coming along and trying to bring up new architectures in Debian. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131025231459.gb31...@riva.ucam.org
