public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Harm Geerts <harmgeerts@home.nl>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: Re: Re: libungif and giflib conflict.
Date: Thu, 3 Nov 2005 03:32:06 +0100	[thread overview]
Message-ID: <200511030332.06816.harmgeerts@home.nl> (raw)
In-Reply-To: <43695F52.1040604@getdesigned.at>

On Thursday 03 November 2005 01:52, Sebastian Redl wrote:
> Duncan wrote:
> >What depclean does is starting from your world file (and including stuff
> >in your system profile that's not specifically listed in the world file),
> >figure out what each package listed there needs to RUN (run-time
> >dependencies, as opposed to compile-time dependencies), BASED ON CURRENT
> >USE FLAGS, then unmerge other packages as unnecessary.
>
> Actually, that's not 100% correct. If that was so, depclean would never
> remove system packages.
>  But it does. On my setup, which is purely udev, depclean wants to
> remove devfsd. It warns me that it wants to remove the system package,
> but it would do it anyway.

devfsd and udev are responsible for managing the /dev filesystem so the system 
profile needs a package that fills this requirement.

# grep dev-manager /usr/portage/profiles/base/packages
virtual/dev-manager

The gentoo developers decided to make this system requirement depend on a 
virtual so the profile becomes more flexible.

# grep dev-manager /usr/portage/profiles/base/virtuals
virtual/dev-manager			sys-fs/udev

And there we have it, the Gentoo developers have decided they want udev to be 
responsible for managing the /dev filesystem. So we can conclude:
1. devfsd is obsolete and replaced by udev
2. if udev is installed (which it should) then the system profiles requirement 
for a dev-manager has been filled
3. devfsd is no longer required for the system profile and can be removed

Why do I get the warning about unmerging a system package?
Because devfsd still provides virtual/dev-manager, virtual/dev-manager is 
still part of the system profile. So even though Gentoo favors udev over 
devfsd, devfsd still provides functionality that the system profile requires. 
And that's why you get that message.

Note: You can safely unmerge devfsd as long as you've got RC_DEVICES set to 
"auto" or "udev" in /etc/conf.d/rc
-- 
gentoo-amd64@gentoo.org mailing list



      reply	other threads:[~2005-11-03  2:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  5:36 [gentoo-amd64] libungif and giflib conflict Nick Currier
2005-11-01  5:52 ` Barry.SCHWARTZ
2005-11-01  6:00   ` Brian Litzinger
2005-11-01  8:36     ` [gentoo-amd64] " Duncan
2005-11-01 15:07       ` Nick Currier
2005-11-01 17:39       ` Brian Litzinger
2005-11-01 18:19         ` [gentoo-amd64] " Duncan
2005-11-02  4:30           ` Nick Currier
2005-11-02 13:09             ` Harm Geerts
2005-11-02 19:42               ` Nick Currier
2005-11-02 20:54               ` [gentoo-amd64] " Duncan
2005-11-02 21:59                 ` Harm Geerts
2005-11-02 23:07                   ` [gentoo-amd64] " Duncan
2005-11-03  0:52                 ` [gentoo-amd64] " Sebastian Redl
2005-11-03  2:32                   ` Harm Geerts [this message]

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=200511030332.06816.harmgeerts@home.nl \
    --to=harmgeerts@home.nl \
    --cc=gentoo-amd64@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