050327 Harry Putnam wrote:
> Being a new user, I'm wanting to get an overview
> of what an average gentooer might do or need to do over a 6mnth period.
it will take a few weeks to get your system how you want it,
but once you've done that, you never need to re-install.
one of the beauties of Gentoo is that you have full control
over how close you want to be to the bleeding edge or utterly reliable:
what you update & when you do it is entirely upto you.
i never -- as in "never" -- do 'emerge world' except with '-Dup' (below).
i made a list of all the pkgs i have installed with 'qpkg -I',
to which i've added dates of installation & a few notes: 1st few lines:
041031 app-admin/fam-2.7.0-r2 [for kdelibs]
W 040425 app-admin/gkrellm-2.1.28-r1 [invoke 'gkrellm2']
W 040314 app-admin/sysklogd-1.4.1-r10 [was system: PP logger]
S 050226 app-arch/bzip2-1.0.2-r5
041031 app-arch/cabextract-1.1 [for xfree]
S 050205 app-arch/cpio-2.6-r1
S 050108 app-arch/gzip-1.3.5-r5
041009 app-arch/ncompress-4.2.4-r1 [for tar: qpkg ~th]
'S' is system, 'W' is world & ' ' is a pkg installed to support another.
every weekend, i do 'esync', which updates the Portage tree in my machine,
updates the 'esearch' database & lists all pkgs which have changed,
hiliting in color those which i have installed
(you need to emerge the pkg 'esearch' to get 'esync').
then i do 'emerge -Dup world' to get another view of what to update,
& decide which pkgs to actually update, testing with 'emerge -pv <pkg>'.
i edit my list of installed pkgs as i do the emerges.
a rule of thumb is to update if you've seen a security alert
-- tho' some may not affect your machine,
eg a local exploit on a single-user desktop --
or if the 1st or 2nd numbers in the pkg name have gone up.
but it's all upto you & that's part of the beauty of Gentoo ... (smile)
--
========================,,============================================
SUPPORT ___________//___, Philip Webb : [EMAIL PROTECTED]
ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies
TRANSIT `-O----------O---' University of Toronto
--
[email protected] mailing list
