From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23811 invoked by uid 1002); 13 Jul 2003 02:55:49 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 28938 invoked from network); 13 Jul 2003 02:55:49 -0000 Content-Type: text/plain; charset="iso-8859-1" From: "Brett I. Holcomb" Reply-To: brettholcomb@charter.net Organization: Holcomb & Associates To: gentoo-dev@gentoo.org Date: Sat, 12 Jul 2003 23:01:24 -0400 X-Mailer: KMail [version 1.3.1] References: <39997.::ffff:129.240.115.161.1058002049.squirrel@webmail.interhost.no > In-Reply-To: <39997.::ffff:129.240.115.161.1058002049.squirrel@webmail.interhost.no > MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: Subject: Re: [gentoo-dev] Ebuild questions X-Archives-Salt: 21c79056-8707-4581-8502-e0e3826c5b13 X-Archives-Hash: 0a1069377a3e5cb205df6ef28dc58c8c Crumbs, my first reply went to Christian instead of the list. Thank you.  I went back and reread that document - I guess I'd forgotten about that section. I've been reading man pages, eclasses, and existing ebuilds so I guess my brain overflowed! That has helped a lot - along with rereading some of the eclasses I've printed. At this point I have my ebuild retrieving the cvs files and unpacking them (that's easy with cvs.eclass ) and I'm about to get it to compile. I had to make my own src_compile that uses some egames.class functions.   This is fun! I haven't done any shell programming on unix/Linux for about 15 years (I've been working VMS systems and have done a lot of DCL work there and I have done some extensive Windows batch - but that hardly counts ). I'll dig into some of the eclasses and see what they do.  I'd like to stay with whatever standards we have - it's just finding out about them all . > > I've been working on creating an ebuild this week and after working with > > it I > > > have some questions about how ebuilds work. > > nice :) > > > 1. I assume that if I add no functions to an ebuild the process is A) > > src_unpack, B) src_compile, C) src_install. In other words there are > three > > > steps or functions that will be executed. If I desire I can make my own > > functions for these but if I don't I get these three steps executed by > emerge. > > Right, but there is more to the story, read section "2. ebuild scripts" in > the link 0. There it is documented 10 such standard functions. For those > of which you do not provide in your ebuild, emerge will do the default > functions. > > [0] http://www.gentoo.org/doc/en/gentoo-howto.xml > > > 2. What is the best way to let the user know what's happening - for > > example, > > > "compiling xyz module now". I notice some builds use einfo to put out > > messages about what you have to do after install (add user to groups, > etc). > > > Are there specific ebuild functions I should use or are plain old echo > > statements okay? > > the pkg_postinst function is often used to place information about what to > after the install, I think using einfo and ewarn is good practice. > > > Thanks. > > np, > > > -- > > > > Brett I. Holcomb > > AKA Grunt <>< > > > > -- > > gentoo-dev@gentoo.org mailing list > > Christian -- Brett I. Holcomb AKA Grunt <>< -- gentoo-dev@gentoo.org mailing list