public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brett I. Holcomb" <brettholcomb@charter.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Ebuild questions
Date: Fri, 11 Jul 2003 21:58:03 -0400	[thread overview]
Message-ID: <auto-000087994567@remt27.cluster1.charter.net> (raw)

I've been working on creating an ebuild this week and after working with it I 
have some questions about how ebuilds work.

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.

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?


Thanks.

-- 

Brett I. Holcomb
AKA Grunt <><

--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-07-12  1:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12  1:58 Brett I. Holcomb [this message]
     [not found] <39997.::ffff:129.240.115.161.1058002049.squirrel@webmail.interhost.no     >
2003-07-13  3:01 ` [gentoo-dev] Ebuild questions Brett I. Holcomb
  -- strict thread matches above, loose matches on Subject: below --
2003-06-11  1:49 Brett I. Holcomb
2003-06-11  3:47 ` Brian Jackson
2003-06-11 23:08   ` Brett I. Holcomb
2003-06-11  6:29 ` Kumba
2003-06-11  6:41 ` Patrick Kursawe
2003-06-11 16:54   ` brett holcomb
2003-06-11  9:05 ` Paul de Vrieze
2002-03-27  6:58 [gentoo-dev] ebuild questions Hector Urtubia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=auto-000087994567@remt27.cluster1.charter.net \
    --to=brettholcomb@charter.net \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox