Hi, On Wed, Feb 29, 2012 at 9:23 PM, Paul Wise <p...@debian.org> wrote: > Personally I think this is completely the wrong approach to take for > compiler hardening flags. The flags should be enabled by default in > upstream GCC and disabled by upstream software where they result in > problems. The compiler hardening flags have been tested over N years > by RHEL, Fedora, Ubuntu, Gentoo and probably others. The approach > Debian is taking (as opposed to Red Hat, Fedora, Ubuntu etc) means > that software compiled outside of the packaging system will not > benefit from the compiler's hardening flags. Doing it in this way also > violates our social contract.
Not sure it's a good idea to reignite this, specially this late into the Wheezy development cycle (and specially in debian-devel). This has already been discussed in detail: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552688 Regards, -- 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/CANVYNa8Lr-FniudT6htrWMGArUfhO9V5f_tc4LST8S8=eai...@mail.gmail.com
