summaryrefslogtreecommitdiff
path: root/man/1/ct.pod
diff options
context:
space:
mode:
authorDaniel Friesel <derf@derf.homelinux.org>2010-01-17 21:25:31 +0100
committerDaniel Friesel <derf@derf.homelinux.org>2010-01-17 21:25:31 +0100
commitb0758b8838ee0409c2bd7758d54dcc9ad9164126 (patch)
tree6157d4648ea818060480799ded5d8d05ad2b0696 /man/1/ct.pod
parentd29fce554f40b881fa13fd23cec825dea59282a4 (diff)
ct(1): Remove EXAMPLES section, add better explanation of ct refresh instead
Diffstat (limited to 'man/1/ct.pod')
-rw-r--r--man/1/ct.pod17
1 files changed, 5 insertions, 12 deletions
diff --git a/man/1/ct.pod b/man/1/ct.pod
index 3f34ec7..3a6a597 100644
--- a/man/1/ct.pod
+++ b/man/1/ct.pod
@@ -68,7 +68,11 @@ If no argument is given, pushes all installed packages
=item B<refresh> [ I<package> ]
Check prereqs and update symlinks of I<package>.
-If no argument is given, refreshs all installed packages
+If no argument is given, refreshes all installed packages
+
+You can think of this as a 'Fake-Upgrade', it is as if the package had been
+upgraded. Therefory, B<refresh> is useful if you want to test a change without
+committing or pushing it.
=item B<remove> I<packages>
@@ -123,17 +127,6 @@ Contains configuration vars
=back
-=head1 EXAMPLES
-
-=over
-
-=item * B<ct refresh caretaker>
-
-'Fake-Upgrade'. Execute the appropiate commands as if the caretaker package had been
-upgraded (useful when you change something but don't want to commit/push yet)
-
-=back
-
=head1 AUTHOR
Daniel Friesel E<lt>derf@derf.homelinux.orgE<gt>