public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] why is Joe part of 'system' ?
Date: Mon, 05 Sep 2005 13:14:00 +0200	[thread overview]
Message-ID: <431C2878.1020506@planet.nl> (raw)
In-Reply-To: <20050905083238.GA7660@sympatico.ca>

Philip Webb schreef:
> 050904 Holly Bostick wrote:
> 
>> I'm surprised no one has said, "Look in  /var/cache/edb/virtuals ,
>> where you will likely see that Joe is set as an in-use
>> virtual/editor(s) on your actual system".
> 
> 
> Yes, it is, along with Vim Gvim & Nano.  However, (1) that file still
> lists
> 
> virtual/alsa sys-kernel/gentoo-dev-sources virtual/dhcpc
> net-misc/dhcpcd virtual/dev-manager sys-fs/devfsd virtual/mpg123
> media-sound/mpg123
> 
> & (2) it was last updated 050122 .
> 
> Re (1), I don't have a sound card & have removed all the sound
> packages, so 'alsa' & 'mpg123' should not be listed: really, sound is
> not a requirement of any kind for a working system; I removed Dhcpcd
> 041114, as it had ceased to be part of 'system'; Devfsd was one of
> the requirements which caused me to ask the question.
> 
> Re (2) & following from (1), the file doesn't seem to be accurate nor
> does it seem to be kept upto-date by anything: the only package I
> emerged 050122 was Bin86 , needed to handle the MBR.
> 
> So thanx for your fresh point, but it really just raised another
> question.
> 
> My basic purpose is to understand how the Gentoo system works &
> sometimes -- probably here -- this uncovers strange activities which
> have been going on underneath some stone unnoticed by everyone.
> 

I would be interested in this question as well, since in the course of
looking at this file I noticed:

sys-fs/devfsd still listed (along with udev) as virtual/dev-manager
(devfsd was still installed, so I uninstalled it and the entry was not
removed);

sys-kernel/mm-sources still listed (along with gentoo-sources) as
providing linux-sources and alsa, despite the fact that all versions of
mm-sources have long been removed (I never used it, actually).

I removed the redundant entries manually, and have so far encountered no
problems (and expect none), but I do find it odd that I had to do that
at all, and would love to know why.

Holly
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-09-05 11:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-04 14:30 [gentoo-user] why is Joe part of 'system' ? Philip Webb
2005-09-04 14:46 ` Mark Knecht
2005-09-04 16:31 ` Edward Catmur
2005-09-04 16:33 ` Mike Williams
2005-09-04 17:42   ` Philip Webb
2005-09-04 18:04     ` [gentoo-user] " Sven Köhler
2005-09-04 18:04       ` Sven Köhler
2005-09-04 18:19     ` [gentoo-user] " Mike Williams
2005-09-04 19:23       ` Holly Bostick
2005-09-05  8:32         ` Philip Webb
2005-09-05  9:16           ` Nagatoro
2005-09-05 11:14           ` Holly Bostick [this message]
2005-09-05 11:29         ` Mike Williams
2005-09-05 11:36         ` Jason Stubbs
2005-09-05 11:44           ` Holly Bostick
2005-09-05 12:27             ` Jason Stubbs
2005-09-04 18:26     ` Willie Wong
2005-09-04 19:01       ` Philip Webb
2005-09-04 19:56     ` Mariusz Pękala

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=431C2878.1020506@planet.nl \
    --to=motub@planet.nl \
    --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