Le samedi 03 septembre 2005 à 00:31 -0700, Steve Langasek a écrit : > Yeah, right. binutils is unmaintained; the issue couldn't possibly be > that you've made poor design decisions in your packages by making them > dependent on kludgy, non-default toolchain options that policy doesn't > require the toolchain to support at all...
Policy? What does binutils working properly have to do with policy? Policy documents existing practice, and existing practice is to use this option. This is a regression in the toolchain for some architectures. No more, no less. If there aren't enough skilled people to fix the toolchain for some architectures, this isn't a good sign for the health of that port. Today, --as-needed can't be fixed, obviously because nobody skilled enough is willing to work on it. What are you going to do if "default" linker options are broken tomorrow? And after all, you're the release manager, so you'll be the one to deal with the horrible mess of gnome-games dependencies when all indirect dependencies are explicit. Great to see how you welcome design decisions taken to ease your work. -- .''`. Josselin Mouette /\./\ : :' : [EMAIL PROTECTED] `. `' [EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
signature.asc
Description: This is a digitally signed message part