From: Michael Kohl <citizen428@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Running commands after a merge (via /etc/portage/package.hooks)
Date: Fri, 24 Sep 2004 10:17:30 +0200 [thread overview]
Message-ID: <20040924101730.7549bd7e@localhost> (raw)
In-Reply-To: <200409232150.38911.jstubbs@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
On Thu, 23 Sep 2004 21:50:38 +0900
Jason Stubbs <jstubbs@gentoo.org> wrote:
> The test function wouldn't work for two reasons. One is that the test
> function is run before the package is merged to the live filesystem.
> Actually, it's run before src_install is even ran. The second reason
> is that it is not run at all for binary packages.
Would it be possible to add something to pkg_postinst which would parse
this proposed new file in /etc/portage?
Regards
--
Michael Kohl <citizen428@gentoo.org>
GnuPG key: http://dev.gentoo.org/~citizen428/citizen428.asc
0x90CA09E3 - 4D21 916E DBCE 72B8 CDC5 BD87 DE2D 91A2 90CA 09E3
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-24 8:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 11:02 [gentoo-portage-dev] Running commands after a merge (via /etc/portage/package.hooks) Elfyn McBratney
2004-09-22 19:46 ` Joseph Booker
2004-09-22 20:46 ` [gentoo-portage-dev] unsuscribe Luca Martinetti
2004-09-22 21:12 ` Michael Kohl
2004-09-24 9:55 ` [gentoo-portage-dev] Running commands after a merge (via /etc/portage/package.hooks) Elfyn McBratney
2004-09-22 19:52 ` Jeff Smelser
2004-09-23 2:56 ` Colin Kingsley
2004-09-23 10:48 ` Sven Vermeulen
2004-09-23 12:50 ` Jason Stubbs
2004-09-24 8:17 ` Michael Kohl [this message]
2004-09-24 8:28 ` Marius Mauch
2004-09-24 9:04 ` Michael Kohl
2004-09-24 9:53 ` Elfyn McBratney
2004-09-24 9:51 ` Elfyn McBratney
2004-09-24 9:47 ` Elfyn McBratney
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=20040924101730.7549bd7e@localhost \
--to=citizen428@gentoo.org \
--cc=gentoo-portage-dev@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