Dave Nebinger posted <[EMAIL PROTECTED]>, excerpted below, on Mon, 03 Oct 2005 01:46:13 -0400:
>> Wouldn't it be better to use the >> associated portage-provided packages? > > That's the goal - strip out the parts from their distribution that have > exiting components already within the portage tree (and already installed on > my system). Boils down to a couple of wars for the most part, plus scripts, > things like that. If you haven't looked at them yet (you may be well past this, it sounds like you are well farther along than I am in ebuilding experience -- I don't think I'd be tackling that job)... * Check out the split kde ebuilds (konqueror, kcontrol, etc, instead of kdebase, kmail, knode, the various handheld/PIM builds, instead of kdepim, etc) to see how an existing in-portage solution manages taking only part of the source and configuring/building based on already merged components from the rest of the source. * Check out the xorg-x11 builds, for a good example of a rather complex ebuild, broken down into logically digestible pieces, in the form of multiple functions within the ebuild. * Both of these use eclasses as well, but the kde ones especially should be instructive for their use of the kde eclasses to handle the various split functionality, if you decide to go with eclasses for part of it. Just because it might be of help... -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-dev@gentoo.org mailing list
