From: "Sean P. Kane" <spkane@genomatica.com>
To: <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] virtual problem
Date: Fri, 31 May 2002 18:12:59 -0700 [thread overview]
Message-ID: <C42D120999B1CC4C886B6BB2832F356019B3A9@HERMES.genomatica.com> (raw)
Virtual/* means that it isn't an exact package and you simply need
something that gives you that service (and is who's ebuild is setup to
claim to provide that service).
i.e. there are a variety of system loggers like metalog, syslogd,
syslogd-ng and they all provide virtual/logger, so that any one of them
will suffice for some thing that depends on virtual/logger. Where-as if
you depended on syslogd, the ebuild would fail for someone using
metalog.
I believe this is covered more here:
http://www.gentoo.org/doc/gentoo-howto.html
Sean
-----Original Message-----
From: Bill Kenworthy [mailto:billk@iinet.net.au]
Sent: Friday, May 31, 2002 16:28
To: gentoo-dev List
Subject: [gentoo-dev] virtual problem
I have not been able to do an "emerge --update world" for a couple of
weeks now due to various vritual/?????????? packages. e.g., xmms
depended on virtual/opengl. I unermerged it and ended up emergeing a
number of other packages in the process of getting it back. Now it is
done one of those packages, qt, complains of missing virtual/glu when I
try and emerge world.
Can someone explain this whole virtual thing and how to fix, or give a
reference in the docs?
BillK
* I have noted a couple of other emails along these lines, but havent
seen any fixes yet.
_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next reply other threads:[~2002-06-01 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 1:12 Sean P. Kane [this message]
2002-06-01 0:47 ` [gentoo-dev] virtual problem Ed Heron
2002-06-01 5:38 ` Bill Kenworthy
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 15:33 Sean P. Kane
2002-05-31 23:28 Bill Kenworthy
2002-01-14 18:13 Sebastian Werner
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=C42D120999B1CC4C886B6BB2832F356019B3A9@HERMES.genomatica.com \
--to=spkane@genomatica.com \
--cc=gentoo-dev@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