Bash示例第三部分.docxVIP

Disclaimer : Disclaimer : The original version of this article was first published on IBM developerWorks, and is property of Westtech Information Services. This document is an updated version of the original article, and contains various improvements made by the Gentoo Linux Documentation team. This document is not actively maintained. Bash by example, Part 3 Content: Exploring the ebuild system Enter the ebuild system Ive really been looking forward to this third and final Bash by example article, because now that weve already covered bash programming fundamentals in Part 1 and Part 2, we can focus on more advanced topics, like bash application development and program design. For this article, I will give you a good dose of practical, real-world bash development experience by presenting a project that Ive spent many hours coding and refining: The Gentoo Linux ebuild system. Im the chief architect of Gentoo Linux, a next-generation Linux OS currently in beta. One of my primary responsibilities is to make sure that all of the binary packages (similar to RPM packages) are created properly and work together. As you probably know, a standard Linux system is not composed of a single unified source tree (like BSD), but is actually made up of about 25+ core packages that work together. Some of the packages include: Package linux Description The actual kernel util-linux A collection of miscellaneous Linux-related programs e2fsprogs A collection of ext2 filesystem-related utilities glibc The GNU C library Each package is in its own tarball and is maintained by separate independent developers, or teams of developers. To create a distribution, each package has to be separately downloaded, compiled, and packaged. Every time a package must be fixed, upgraded, or improved, the compilation and packaging steps must be repeated (and this gets old really fast). To help eliminate the repetitive steps involved in creating and updating packages, I created the ebuild system, written al