Obsoleting ports

[Joseph S. Myers]

On Sat, 9 Oct 2004, Kazu Hirata wrote:

> Now that we are in stage 3, I am wondering if it's a good time to
> start thinking about obsoleting ports.

Not all port maintainers can necessarily handle the GCC list volume, so I 
think you ought to contact the maintainers of the listed ports (except for 
arc which has no listed maintainer) directly with the reasons for thinking 
the port not adequately maintained (e.g., cc1 hasn't built since before 
3.4, or ICE building libgcc since before 3.4, or lack of recent testsuite 
results on gcc-testresults in the case of hosted systems capable of 
running dejagnu) and ascertain whether they have any plans for fixing the 
port before 4.0 releases (if expected to be effectively dead in 4.0, being 
obsoleted there does make sense) - or, better, plans to move it away from 
obsolete features described in backends.html.  If the listed maintainer 
believes the port to be dead or no longer wishes to maintain it, that's 
also a reason to obsolete it unless someone else wishes to take over.  
Contacting anyone who has expressed an interest in working on any of the 
ports makes sense as well.  Likewise GCC maintainers for operating systems 
using any of those ports which use GCC as system compiler.

-- 
Joseph S. Myers               http://www.srcf.ucam.org/~jsm28/gcc/
    jsm@polyomino.org.uk (personal mail)
    joseph@codesourcery.com (CodeSourcery mail)
    jsm28@gcc.gnu.org (Bugzilla assignments and CCs)