On Tue, Jun 10, 2008 at 12:50:34PM +0200, Sam Ravnborg wrote: > > > > When did this policy change, so that it's now acceptable to depend on > > Perl, which is roughly equivalent as a tool dependency? > > We have perl as a mandatory part of the kernel build in several places > for various architectures. > And I do not recall anyone submitting a bug that they could not build > a kernel due to the perl dependency. > But I am obviously well aware of that we use it for the time stuff. > And plenty of places in scripts/ have dependencies on either perl or python already (and have for some time). Both are pretty ubiquitous these days, whether people like it or not. There's not much point in trying to keep the build limping along for people who don't want to set up these tools on their platforms, since they're going to lose out on half of the functionality anyways (checkstack, bloat-o-meter, etc.). Building natively is a good stress tester, and does find a lot of bugs. For that same reason, if you can build the kernel, you can build python and perl natively on your platform, too. Some of us have already been doing this for ages and have no idea what the fuss is about. -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
