Re: gcc best practices | problems
>>>>> Steve Langasek <email@example.com> writes:
> If the package doesn't compile with gcc-4.0 because your code needs to be
> updated, you should fix your code. You should only depend on older
> compiler versions in the case of a bug in the current version (or in
> exceptional cases, such as a kernel or libc needing a particular compiler
> version because the package abuses the compiler).
What about packages not actively maintained upstream? In my case (jlint),
the fix was relatively easy but it in some cases the fix may not be obvious
to the maintainer.
Ganesan Rajagopal (rganesan at debian.org) | GPG Key: 1024D/5D8C12EA
Web: http://employees.org/~rganesan | http://rganesan.blogspot.com