Because there shouldn't be one. There was no warning when the default
X switched from XFree to X.org, because non-broken programs don't know
the difference. There is no warning when upgrading gcc from 2.x to
3.x to 4.x, despite it being well known that that breaks MANY build
processes.
On 2/4/07, Ulrich Lukas <email address hidden> wrote:
> I just lost half a day figuring out why several configure scripts who
> ran perfectly under Dapper are broken in Edgy.
>
> Why isn't there at least a warning or note indicating the changed
> defaults?
Because there shouldn't be one. There was no warning when the default
X switched from XFree to X.org, because non-broken programs don't know
the difference. There is no warning when upgrading gcc from 2.x to
3.x to 4.x, despite it being well known that that breaks MANY build
processes.
On 2/4/07, Ulrich Lukas <email address hidden> wrote:
> I just lost half a day figuring out why several configure scripts who
> ran perfectly under Dapper are broken in Edgy.
>
> Why isn't there at least a warning or note indicating the changed
> defaults?