Stefan Tauner wrote:
Heavily influenced by a discussion with (and based on code from) Peter Stuge.
Peter Stuge argued all evening with me that the mandatory -p parameter is a regression and should be fixed, because the common case is -p internal and that was the default programmer for most of the installations especially those users that dont know what they are doing. While i don't think that the internal programmer should be the new default default (sic) programmer i do see the point in having a default programmer and don't think that the "some user used to one default programmer could easily break $stuff when using another build" outweighs the freedom of maintainers to shoot their users in the foot especially if they are the same person. ;)
We can not force any distributor to have no default programmer anyway, a patch that adds one is trivial. Having this build time option does not neccessarily make us endorsing this option either: If we deem it worth it, we could add a build warning and add a note in the Makefile/README to make maintainers consider our arguments.
Signed-off-by: Stefan Tauner stefan.tauner@student.tuwien.ac.at
Acked-by: Peter Stuge peter@stuge.se