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: faq.xml
Date: Thu, 13 Oct 2011 16:58:14 +0000 (UTC) [thread overview]
Message-ID: <20111013165814.C84602004B@flycatcher.gentoo.org> (raw)
swift 11/10/13 16:58:14
Modified: faq.xml
Log:
Add information on --with-bdeps as per discussion on gentoo-dev
Revision Changes Path
1.120 xml/htdocs/doc/en/faq.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/faq.xml?rev=1.120&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/faq.xml?rev=1.120&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/faq.xml?r1=1.119&r2=1.120
Index: faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/faq.xml,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -r1.119 -r1.120
--- faq.xml 11 Sep 2011 08:43:18 -0000 1.119
+++ faq.xml 13 Oct 2011 16:58:14 -0000 1.120
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/faq.xml,v 1.119 2011/09/11 08:43:18 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/faq.xml,v 1.120 2011/10/13 16:58:14 swift Exp $ -->
<guide>
<title>Gentoo Linux Frequently Asked Questions</title>
@@ -47,8 +47,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>6</version>
-<date>2011-09-11</date>
+<version>7</version>
+<date>2011-10-13</date>
<faqindex>
<title>Questions</title>
@@ -204,14 +204,21 @@
<p>
In fact, there is no difference between the various releases after they have
-been installed. Gentoo 1.4 and later are <c>glibc-2.3.x</c> based. As such,
-running <c>emerge --sync && emerge -uDN world</c> will bring your
+been installed. Gentoo 1.4 and later are <c>glibc-2.3.x</c> (or higher) based.
+As such, running <c>emerge --sync && emerge -uDN world</c> will bring your
entire system up to speed with the "latest Gentoo". The differences between
individual releases lie in the installation medium and pre-compiled packages.
See the <uri link="/doc/en/gentoo-upgrading.xml">Gentoo Upgrading Guide</uri>
for more information about profiles and their role in upgrading.
</p>
+<p>
+Also note that the <c>emerge -uDN world</c> command updates the packages you
+have installed as well as its dependencies, but not the build-time dependencies
+(packages needed during builds but not when the software is installed). To
+update those as well, add the <c>--with-bdeps=y</c> option.
+</p>
+
</body>
</section>
<section id="bootrescue">
next reply other threads:[~2011-10-13 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 16:58 Sven Vermeulen (swift) [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-09 19:45 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: faq.xml Sven Vermeulen (swift)
2012-12-01 7:26 Joshua Saddler (nightmorph)
2010-10-14 6:09 Joshua Saddler (nightmorph)
2010-07-16 23:18 Joshua Saddler (nightmorph)
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=20111013165814.C84602004B@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