From d632b7bc0d9518d91ee0003d1a88ad43b259832e Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Tue, 11 Dec 2007 21:32:44 +0000 Subject: Add some documentation for ebuild phases and pre/post phase hooks that can be defined via bashrc. (trunk r8876) svn path=/main/branches/2.1.2/; revision=8879 --- doc/package/ebuild.docbook | 4 ++++ doc/package/ebuild/phases.docbook | 43 +++++++++++++++++++++++++++++++++++++++ 2 files changed, 47 insertions(+) create mode 100644 doc/package/ebuild.docbook create mode 100644 doc/package/ebuild/phases.docbook (limited to 'doc/package') diff --git a/doc/package/ebuild.docbook b/doc/package/ebuild.docbook new file mode 100644 index 000000000..5466f99db --- /dev/null +++ b/doc/package/ebuild.docbook @@ -0,0 +1,4 @@ + +Ebuild +&package_ebuild_phases; + diff --git a/doc/package/ebuild/phases.docbook b/doc/package/ebuild/phases.docbook new file mode 100644 index 000000000..5c7f04969 --- /dev/null +++ b/doc/package/ebuild/phases.docbook @@ -0,0 +1,43 @@ + + Ebuild Phases + + Ebuild execution is divided into a series of phases. In order + to implement a phase, an ebuild defines a function to serve as + an entry point for execution of that phase. + This design is similar to the template method pattern that + is commonly used in object oriented programming languages. An ebuild + can inherit or override a template method from an eclass. + + + The function names for the ebuild phases, listed in order of execution: + + + pkg_setup + + + src_unpack + + + src_compile + + + src_test + + + src_install + + + pkg_preinst + + + pkg_postinst + + + pkg_prerm + + + pkg_postrm + + + + -- cgit v1.2.3-1-g7c22