aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJason Woodward2003-11-18 15:47:19 +0000
committerJason Woodward2003-11-18 15:47:19 +0000
commit7ee104dd0ed6bea43987561faee9311c0e9512a6 (patch)
treebf7a0f38c5ef91b4ded9149deecd0e3e1263d0c2
parent5064ec3ff97aa909b2eb0a8996f5905c92b14282 (diff)
downloadslapt-get-7ee104dd0ed6bea43987561faee9311c0e9512a6.tar.gz
added 30. I am tracking current, how do I keep the base disk set up to date?
-rw-r--r--FAQ9
1 files changed, 9 insertions, 0 deletions
diff --git a/FAQ b/FAQ
index 4af2b50..3dee66f 100644
--- a/FAQ
+++ b/FAQ
@@ -28,6 +28,7 @@ Frequenty Asked Questions:
27. How can I exclude all *pre* and *beta* packages safely?
28. How does the transaction engine work?
29. How does the package version comparison algorithm work?
+30. I am tracking current, how do I keep the base disk set up to date?
@@ -560,3 +561,11 @@ Frequenty Asked Questions:
are compared via strcmp. This is a fallback mechanism.
+30. I am tracking current, how do I keep the base disk set up to date?
+
+ If you are tracking current, --dist-upgrade may be more useful than --upgrade.
+
+ Even if you aren't intentionally switching to a newer distribution,
+ --dist-upgrade will ensure that the base set is always present while at the
+ same time keeping your installed packages up to date.
+