Difference between revisions of "Emerge"
From Funtoo Linux
(Created page with "== Emerge == === The recommended way to update your system === <pre> # emerge --sync # emerge -auDN world --jobs=3 </pre> === Emerge Options === ; --with-bdeps=y : This optio...") |
|||
| Line 12: | Line 12: | ||
; --with-bdeps=y | ; --with-bdeps=y | ||
: This option tells Portage to consider DEPEND for already-installed packages (that are not required to be considered) when updating your system. So when used with <tt>-uDN @world</tt>, the<tt> --with-bdeps=y</tt> option will cause any updated packages listed in DEPEND @world set's ebuilds -- not just those packages being installed/updated -- to be upgraded. However, if any updates are made to a package's DEPEND, it will not cause the specific package(s) containing the DEPEND to be rebuilt, so that they were explicitly built against the packages that were just upgraded. To Daniel Robbins, this seems like a half-step rather than the full upgrade step. It would be preferable if there were an option to cause any parent packages to be rebuilt if anything in DEPEND were upgraded. The reason for this is that if there is a change in DEPEND, then there is the ''potential'' for the parent ebuild to also be affected by these changes in any number of ways. So rebuilding against the most recently-upgraded DEPEND is generally safest. | : This option tells Portage to consider DEPEND for already-installed packages (that are not required to be considered) when updating your system. So when used with <tt>-uDN @world</tt>, the<tt> --with-bdeps=y</tt> option will cause any updated packages listed in DEPEND @world set's ebuilds -- not just those packages being installed/updated -- to be upgraded. However, if any updates are made to a package's DEPEND, it will not cause the specific package(s) containing the DEPEND to be rebuilt, so that they were explicitly built against the packages that were just upgraded. To Daniel Robbins, this seems like a half-step rather than the full upgrade step. It would be preferable if there were an option to cause any parent packages to be rebuilt if anything in DEPEND were upgraded. The reason for this is that if there is a change in DEPEND, then there is the ''potential'' for the parent ebuild to also be affected by these changes in any number of ways. So rebuilding against the most recently-upgraded DEPEND is generally safest. | ||
| + | |||
| + | |||
| + | [[Category:Portage]] | ||
Latest revision as of 01:21, 18 January 2011
[edit] Emerge
[edit] The recommended way to update your system
# emerge --sync # emerge -auDN world --jobs=3
[edit] Emerge Options
- --with-bdeps=y
- This option tells Portage to consider DEPEND for already-installed packages (that are not required to be considered) when updating your system. So when used with -uDN @world, the --with-bdeps=y option will cause any updated packages listed in DEPEND @world set's ebuilds -- not just those packages being installed/updated -- to be upgraded. However, if any updates are made to a package's DEPEND, it will not cause the specific package(s) containing the DEPEND to be rebuilt, so that they were explicitly built against the packages that were just upgraded. To Daniel Robbins, this seems like a half-step rather than the full upgrade step. It would be preferable if there were an option to cause any parent packages to be rebuilt if anything in DEPEND were upgraded. The reason for this is that if there is a change in DEPEND, then there is the potential for the parent ebuild to also be affected by these changes in any number of ways. So rebuilding against the most recently-upgraded DEPEND is generally safest.
