From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] post build files
Date: Tue, 9 Sep 2014 13:41:05 -0400 [thread overview]
Message-ID: <CAGfcS_mKyjuZrMjtdZkCZVg9oaBOhP95zxqQxdR8hjkbQCvwVw@mail.gmail.com> (raw)
In-Reply-To: <loom.20140909T164818-641@post.gmane.org>
On Tue, Sep 9, 2014 at 11:20 AM, James <wireless@tampabay.rr.com> wrote:
> I'm rather new to hacking ebuilds. I have read most every doc
> I can find on the subject. One thing I'm looking for is a post-build
> document that shows me the path/name of everything built.
If you literally want a list of everything that was installed by a
Gentoo ebuild, then the simplest thing is to run qlist from
app-portage/portage-utils.
Of course, the list of what a package /could/ install can vary based
on USE flags or environment.
If you're trying to learn how ebuilds work, devmanual.gentoo.org is
the definitive resource. If you have specific questions feel free to
ask, but just about anything you want to know is there. By all means
try reading a few ebuilds to get a hang for things as well, but I'd
start with simple ones (avoid trying to learn by looking at packages
that use complex eclasses). The simplest ebuilds tend to be for
simple, standalone programs.
Keep in mind that ebuilds work by extending functions defined by PMS,
so an ebuild can contain fairly little content and yet be fairly
functional (the default functions are running for most of the build
phases). The idea is if all a package does is run configure ; make ;
make install it often needs almost nothing in the ebuild to work.
--
Rich
next prev parent reply other threads:[~2014-09-09 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 15:20 [gentoo-user] post build files James
2014-09-09 16:23 ` Alec Ten Harmsel
2014-09-11 14:02 ` [gentoo-user] " James
2014-09-09 17:41 ` Rich Freeman [this message]
2014-09-11 16:20 ` James
2014-09-11 19:08 ` Alec Ten Harmsel
2014-09-11 19:27 ` Alec Ten Harmsel
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=CAGfcS_mKyjuZrMjtdZkCZVg9oaBOhP95zxqQxdR8hjkbQCvwVw@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.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