This is a pet peeve of mine on Free Software projects in general - The
Program That Wouldn't Compile.
It would seem to me that in the context of the kernel, what is needed is
a BROKEN flag.
An item with a BROKEN flag would NOT be built in an ALLYES or ALLMODULE
configuration - it would require the user to explicitly enable the item
in the configuration, and the user would be notified that the module in
question was not compiling/linking the last time the configuration data
was updated by the kernel team.
That way, a busted item would not be built by default, and the item's
users would be motivated to correct it (and thus remove the stigma of
the BROKEN flag).
If an item stays BROKEN for too long, bu-bye! Obviously no-one cares
enough to fix it.
But that's just my opinion.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:32 EST