From: "Sven Vermeulen (swift)" <swift@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/hardened: hardenedfaq.xml
Date: Mon, 31 Dec 2012 19:06:20 +0000 (UTC) [thread overview]
Message-ID: <20121231190620.163A02171D@flycatcher.gentoo.org> (raw)
swift 12/12/31 19:06:20
Modified: hardenedfaq.xml
Log:
Explain what to do with failed built packages
Revision Changes Path
1.31 xml/htdocs/proj/en/hardened/hardenedfaq.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/hardenedfaq.xml?rev=1.31&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/hardenedfaq.xml?rev=1.31&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/hardenedfaq.xml?r1=1.30&r2=1.31
Index: hardenedfaq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/hardenedfaq.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- hardenedfaq.xml 28 Oct 2012 15:21:06 -0000 1.30
+++ hardenedfaq.xml 31 Dec 2012 19:06:19 -0000 1.31
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/hardenedfaq.xml,v 1.30 2012/10/28 15:21:06 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/hardenedfaq.xml,v 1.31 2012/12/31 19:06:19 swift Exp $ -->
<guide lang="en">
<title>Gentoo Hardened Frequently Asked Questions</title>
@@ -31,8 +31,8 @@
the gentoo-hardened mailing list.
</abstract>
-<version>3.4</version>
-<date>2011-3-27</date>
+<version>4</version>
+<date>2012-12-31</date>
<faqindex>
<title>Questions</title>
@@ -319,7 +319,9 @@
<p>
The <c>--keep-going</c> option is added to ensure emerge won't stop in case any
-package fails to build.
+package fails to build. If that occurs however, you need to make sure that the
+remainder of the packages is built. You can check the output of emerge at the
+end to find out which packages were not rebuilt.
</p>
</body>
next reply other threads:[~2012-12-31 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 19:06 Sven Vermeulen (swift) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-21 15:53 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/hardened: hardenedfaq.xml Francisco Blas Izquierdo Riera (klondike)
2013-01-21 15:50 Francisco Blas Izquierdo Riera (klondike)
2013-01-21 15:49 Francisco Blas Izquierdo Riera (klondike)
2013-01-12 12:44 Magnus Granberg (zorry)
2011-03-29 1:57 Magnus Granberg (zorry)
2011-01-29 15:17 JosA MarAa Alonso (nimiux)
2011-01-25 23:07 Magnus Granberg (zorry)
2010-08-17 22:35 Angelo Arrifano (miknix)
2010-08-07 13:31 Angelo Arrifano (miknix)
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=20121231190620.163A02171D@flycatcher.gentoo.org \
--to=swift@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-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