On Tue, 2004-01-27 at 05:04, Drake Wyrm wrote: > When ebuild.sh is called to perform one of the steps of a merge, it mostly > uses one of the dyn_* functions to perform the task. The dyn_* function, > in turn, usually does some prepwork, calls a pkg_* or src_* function, > and does some followup. My questions are in regard to the meaning of > those prefixes. The "pkg_" and "src_" prefixes seem descriptive enough, > but unnecessary. Why were "src_unpack", "src_compile", and "src_install" > chosen vice "pkg_unpack", etc.? What does "dyn" refer to, anyway? > > I know these questions probably seem rather pointless, but those names > mean (or meant) something to somebody. I am trying to understand what > the designers of Portage were thinking to help me understand how Portage > works.
Well, I am going to take a shot here. Even though I am not a portage developer, I would think that the src_ names only deal with actualsource code, whereas the pkg_ names deal with "packages" as a whole. Remember that Gentoo now also has support for binary packages, along with building straight from source. The pkg_ steps are common to both packages and source, whereas the src_ steps are for source builds only. -- Chris Gianelloni Developer, Gentoo Linux Games Team Is your power animal a penguin?
signature.asc
Description: This is a digitally signed message part
