From: "Sven Vermeulen (swift)" <swift@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-portage-advanced.xml
Date: Tue, 7 Feb 2012 19:17:59 +0000 (UTC) [thread overview]
Message-ID: <20120207191759.0CC2C2004B@flycatcher.gentoo.org> (raw)
swift 12/02/07 19:17:59
Modified: hb-portage-advanced.xml
Log:
It is pkg_postinst, not src_postinst. Thanks to Agostino Sarubbo for noticing/notifying
Revision Changes Path
1.2 xml/htdocs/doc/en/handbook/hb-portage-advanced.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-portage-advanced.xml?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-portage-advanced.xml?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-portage-advanced.xml?r1=1.1&r2=1.2
Index: hb-portage-advanced.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-advanced.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-portage-advanced.xml 15 Jan 2012 09:55:35 -0000 1.1
+++ hb-portage-advanced.xml 7 Feb 2012 19:17:58 -0000 1.2
@@ -4,7 +4,7 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-advanced.xml,v 1.1 2012/01/15 09:55:35 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-advanced.xml,v 1.2 2012/02/07 19:17:58 swift Exp $ -->
<sections>
@@ -15,8 +15,8 @@
features.
</abstract>
-<version>1</version>
-<date>2012-01-15</date>
+<version>2</version>
+<date>2012-02-07</date>
<section>
<title>Introduction</title>
@@ -121,7 +121,7 @@
<p>
When Portage works with ebuilds, it uses a bash environment in which it calls
-the various build functions (like src_prepare, src_configure, src_postinst,
+the various build functions (like src_prepare, src_configure, pkg_postinst,
etc.). But Portage also allows you to set up a bash environment yourself.
</p>
next reply other threads:[~2012-02-07 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 19:17 Sven Vermeulen (swift) [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-06 20:17 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-portage-advanced.xml Sven Vermeulen (swift)
2012-10-06 20:19 Sven Vermeulen (swift)
2013-04-11 18:27 Sven Vermeulen (swift)
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=20120207191759.0CC2C2004B@flycatcher.gentoo.org \
--to=swift@gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@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