From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ebuild Fixup Scripts
Date: Sat, 21 Aug 2010 16:16:46 +0200 [thread overview]
Message-ID: <201008211616.46558.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <AANLkTimkN3b8AR_TCPzvAok7=Hefe0U=5S8_vnjD7NJE@mail.gmail.com>
Apparently, though unproven, at 16:10 on Saturday 21 August 2010, Carl Pettit
did opine thusly:
> A lot of ebuilds list a fixup script at the end that the user must manually
> execute. If the build is pulled in as part of another build, these scripts
> can be missed. This fact has cost me 2 days and a borked system. Is there a
> way of running these automatically on completion as part of the install?
No, there is no such thing and will likely never be.
The default operation of gentoo is to put stuff there and wait for you (root)
to take action on it.
ebuilds do configure dick with your configs (OK, except webmin, but that is a
piece of shit and to be expected), start daemons or cause them to be added to
rc-update. That is for YOU - as root - to decide and act on. User wanting a
distro that does everything for them need use Red Hat, Ubuntu, etc.
What you must do is configure your elogging in make.conf (it's all in man 5
make.conf) and read the elogs in /var/log/portage/elog/ when an emerge is
complete. Or have them mailed to you.
--
alan dot mckinnon at gmail dot com
prev parent reply other threads:[~2010-08-21 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 14:10 [gentoo-user] Ebuild Fixup Scripts Carl Pettit
2010-08-21 14:16 ` Alan McKinnon [this message]
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=201008211616.46558.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--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