From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge --update behavior
Date: Mon, 2 Jan 2012 08:01:15 -0800 [thread overview]
Message-ID: <CAK2H+ecz2A-kAN81w9PMU56Mqb5i1e4sEEHMOvjQ58tbKSRPeg@mail.gmail.com> (raw)
In-Reply-To: <4F01CED2.5090806@libertytrek.org>
On Mon, Jan 2, 2012 at 7:35 AM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
> On 2012-01-01 6:22 PM, Mark Knecht <markknecht@gmail.com> wrote:
>>
>> 2) I forget the -1 sometimes when I do an individual package update.
>> However I generally remember to go back and hand edit the world file
>> once a quarter or so and remove anything that isn't a real
>> application, etc.
>
>
> How do you tell which is which?
>
I tell by knowing which files I want in @world. Everything in world
should be a package __I__ specifically want to use. Everything in
world (on my machines anyway) is something:
1) I'd call from the command line
2) Need to write a little software myself, most specifically a library
3) Aid in displaying things, like font packages
4) Something required by Gentoo that I don't totally understand, like
a virtual package.
I just look through every so often and make sure everything seems to
meet those sorts of requirements. When I find a library or something
else then:
1) I make sure I'm clean with emerge -DuN @world AND emerge -p --depclean
2) I'll delete the questionable item
3) I'll see what happens with the two commands in #1
To me it's pretty straight forward, but I'm also not bothered at all
by the idea that emerge package and emerge -u package do the same
thing. A machine that doesn't have a package, when updated, should
have the package and it should (IMO) be in world, but that's just me.
HTH,
Mark
mark@c2stable ~ $ cat /var/lib/portage/world
app-admin/syslog-ng
app-benchmarks/bonnie++
app-benchmarks/iozone
app-cdr/cdrtools
app-cdr/dvd+rw-tools
app-editors/vim
app-emulation/virtualbox
app-emulation/virtualbox-extpack-oracle
app-emulation/vmware-player
app-forensics/chkrootkit
app-misc/screen
app-pda/gtkpod
app-pda/ifuse
app-portage/eix
app-portage/gentoolkit
app-portage/layman
app-portage/portage-utils
app-text/acroread
dev-util/nvidia-cuda-sdk
dev-util/nvidia-cuda-toolkit
dev-util/strace
dev-vcs/subversion
kde-base/kde-meta
mail-client/mailx
mail-mta/ssmtp
media-fonts/font-bitstream-100dpi
media-fonts/font-bitstream-75dpi
media-fonts/font-bitstream-speedo
media-fonts/font-bitstream-type1
media-fonts/freefont-ttf
media-fonts/freefonts
media-fonts/ttf-bitstream-vera
media-gfx/imagemagick
media-libs/exiftool
media-libs/mesa
media-sound/alsa-tools
media-sound/alsa-utils
media-video/dvdbackup
media-video/handbrake
media-video/nvidia-settings
media-video/smplayer
media-video/vobcopy
media-video/xine-ui
net-analyzer/nettop
net-dns/noip-updater
net-fs/samba
net-im/skype
net-misc/ntp
net-misc/rdesktop
net-misc/telnet-bsd
net-misc/tightvnc
net-misc/unison
net-misc/whois
sci-libs/ta-lib
sys-apps/dstat
sys-apps/hdparm
sys-apps/hwinfo
sys-apps/less
sys-apps/lshw
sys-apps/microcode-ctl
sys-apps/mlocate
sys-apps/portage
sys-apps/smartmontools
sys-boot/grub-static
sys-fs/dosfstools
sys-fs/fuse
sys-fs/mdadm
sys-kernel/gentoo-sources
sys-kernel/gentoo-sources:3.1.0-r1
sys-kernel/module-rebuild
sys-power/apcupsd
sys-power/cpufrequtils
sys-power/powertop
sys-process/iotop
sys-process/lsof
sys-process/time
sys-process/vixie-cron
virtual/jdk
virtual/jre
www-client/firefox
www-plugins/adobe-flash
www-servers/thttpd
x11-apps/mesa-progs
x11-apps/xclock
x11-apps/xhost
x11-base/xorg-drivers
x11-base/xorg-server
x11-drivers/nvidia-drivers
x11-drivers/xf86-input-evdev
x11-drivers/xf86-input-virtualbox
x11-drivers/xf86-video-fbdev
x11-drivers/xf86-video-virtualbox
x11-misc/driconf
x11-misc/read-edid
x11-misc/xsnap
mark@c2stable ~ $
next prev parent reply other threads:[~2012-01-02 16:03 UTC|newest]
Thread overview: 108+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-01 21:50 [gentoo-user] emerge --update behavior Michael Orlitzky
2012-01-01 22:06 ` Michael Mol
2012-01-01 22:13 ` Michael Orlitzky
2012-01-01 22:31 ` Dale
2012-01-01 22:40 ` Mark Knecht
2012-01-01 22:49 ` Dale
2012-01-01 22:54 ` Claudio Roberto França Pereira
2012-01-01 23:06 ` Dale
2012-01-01 23:07 ` Michael Orlitzky
2012-01-01 23:07 ` Michael Orlitzky
2012-01-01 23:22 ` Mark Knecht
2012-01-02 15:35 ` Tanstaafl
2012-01-02 15:47 ` Michael Orlitzky
2012-01-02 15:53 ` Michael Mol
2012-01-02 16:01 ` Mark Knecht [this message]
2012-01-02 16:09 ` Michael Orlitzky
2012-01-02 16:16 ` Michael Mol
2012-01-02 16:20 ` Michael Mol
2012-01-02 23:33 ` Alan McKinnon
2012-01-03 0:01 ` Michael Mol
2012-01-02 16:33 ` Michael Orlitzky
2012-01-02 17:06 ` Michael Mol
2012-01-02 17:39 ` Michael Orlitzky
2012-01-02 17:45 ` Michael Mol
2012-01-02 17:55 ` Michael Orlitzky
2012-01-02 18:07 ` Michael Mol
2012-01-02 18:20 ` Michael Orlitzky
2012-01-02 20:50 ` Neil Bothwick
2012-01-02 21:08 ` Michael Orlitzky
2012-01-02 21:25 ` Neil Bothwick
2012-01-02 21:33 ` Michael Orlitzky
2012-01-02 22:41 ` Neil Bothwick
2012-01-02 23:11 ` Michael Orlitzky
2012-01-02 23:29 ` Alan McKinnon
2012-01-02 23:48 ` Michael Orlitzky
2012-01-03 7:46 ` Alan McKinnon
2012-01-03 19:48 ` Walter Dnes
2012-01-03 0:01 ` Neil Bothwick
2012-01-02 23:25 ` Alan McKinnon
2012-01-02 23:49 ` Michael Orlitzky
2012-01-03 0:04 ` Neil Bothwick
2012-01-03 0:22 ` Dale
2012-01-03 2:00 ` Michael Orlitzky
2012-01-03 13:00 ` Mick
2012-01-03 2:00 ` Michael Orlitzky
2012-01-03 11:09 ` Neil Bothwick
2012-01-02 17:47 ` Mark Knecht
2012-01-02 17:55 ` Michael Mol
2012-01-02 17:58 ` Michael Orlitzky
2012-01-03 14:05 ` Hinnerk van Bruinehsen
2012-01-03 14:47 ` Alan McKinnon
2012-01-03 14:51 ` Hinnerk van Bruinehsen
2012-01-03 14:54 ` (Was) " Michael Mol
2012-01-03 14:55 ` Michael Mol
2012-01-03 16:00 ` Mick
2012-01-03 16:18 ` Michael Mol
2012-01-03 17:39 ` Mick
2012-01-03 17:43 ` Michael Mol
2012-01-03 17:52 ` Hinnerk van Bruinehsen
2012-01-03 18:12 ` Mick
2012-01-03 18:21 ` Michael Mol
2012-01-03 17:25 ` Michael Mol
2012-01-02 21:11 ` Alan McKinnon
2012-01-02 21:18 ` Michael Orlitzky
2012-01-02 21:28 ` Neil Bothwick
2012-01-02 21:37 ` Michael Orlitzky
2012-01-02 21:34 ` Michael Mol
2012-01-02 21:48 ` Michael Orlitzky
2012-01-02 21:58 ` Michael Mol
2012-01-02 22:13 ` Michael Orlitzky
2012-01-02 22:45 ` Michael Mol
2012-01-02 23:12 ` Alan McKinnon
2012-01-02 21:20 ` Neil Bothwick
2012-01-02 16:22 ` Mark Knecht
2012-01-02 16:33 ` Michael Orlitzky
2012-01-02 16:59 ` Neil Bothwick
2012-01-02 17:04 ` Neil Bothwick
2012-01-02 16:57 ` Neil Bothwick
2012-01-02 17:29 ` Mark Knecht
2012-01-02 17:47 ` Michael Orlitzky
2012-01-02 20:48 ` Neil Bothwick
2012-01-03 11:49 ` Tanstaafl
2012-01-03 12:04 ` Neil Bothwick
2012-01-04 11:57 ` Pandu Poluan
2012-01-02 18:14 ` Graham Murray
2012-01-02 0:09 ` Neil Bothwick
2012-01-02 0:24 ` Michael Orlitzky
2012-01-02 9:19 ` Neil Bothwick
2012-01-02 10:06 ` Alan McKinnon
2012-01-02 10:18 ` Mick
2012-01-02 13:46 ` Michael Orlitzky
2012-01-02 15:31 ` Tanstaafl
2012-01-02 15:47 ` Michael Orlitzky
2012-01-02 15:47 ` Michael Mol
2012-01-01 22:12 ` Dale
2012-01-02 9:58 ` Alan McKinnon
2012-01-02 10:19 ` Dale
2012-01-02 10:56 ` Alan McKinnon
2012-01-02 11:06 ` Dale
2012-01-02 13:36 ` Neil Bothwick
2012-01-02 13:50 ` Michael Orlitzky
2012-01-02 14:02 ` Neil Bothwick
2012-01-02 14:50 ` Michael Mol
2012-01-02 15:05 ` Alan McKinnon
2012-01-02 15:26 ` Michael Orlitzky
2012-01-02 16:25 ` Frank Steinmetzger
2012-01-02 16:34 ` Michael Orlitzky
2012-01-02 18:38 ` Dale
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=CAK2H+ecz2A-kAN81w9PMU56Mqb5i1e4sEEHMOvjQ58tbKSRPeg@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@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