This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Obsoleting c4x last minute for 4.0


On Wed, 2005-04-06 at 00:30, Mark Mitchell wrote:
> Joe Buck wrote:

> > 
> > But if it won't even build, then users should be warned.
> 
> I suppose -- but we have relatively many configurations that probably 
> won't build, at least if you start combining various options, and 
> including langauges beyond just C and C++.
> 
> I'd be content with a patch that issued a warning, but declaring a port 
> obsolete has often been contentions, and I'd hate to rush into it.

Maybe we need a third category - 'at risk'.  Such a port will typically
have no active maintainer, some likely serious bugs and might at some
future date be obsoleted if no maintainer steps forward.

We could put several ports into that category and it shouldn't have the
negative stigma that obsolete seems to have.

R.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]