From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] virtual/eject ?
Date: Fri, 27 May 2005 09:44:28 -0400 [thread overview]
Message-ID: <1117201469.14290.232.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <200505270202.27276@enterprise.flameeyes.is-a-geek.org>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Fri, 2005-05-27 at 02:02 +0200, Diego 'Flameeyes' Pettenò wrote:
> On Monday 23 May 2005 18:12, Diego 'Flameeyes' Pettenò wrote:
> > This can't be done everytime, and hoping for, in future, having an
> > universal eject (libcdio should allow that) I wanted to ask if is possible
> > to add a virtual/eject provided by sys-apps/eject and sys-apps/eject-bsd so
> > that they can be made dependencies as needed.
> News about this? We really need a solution to this.
I'm just curious, but why exactly is a virtual needed?
Why can't it be something like:
!blah? ( sys-apps/eject )
blah? (sys-apps/eject-bsd )
A virtual is usually reserved for when it affects a large number of
packages. If it affects one or two, then simply using some fun *DEPEND
syntax usually covers the issue.
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-27 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 16:12 [gentoo-dev] virtual/eject ? Diego 'Flameeyes' Pettenò
2005-05-23 17:16 ` Ciaran McCreesh
2005-05-23 17:27 ` Diego 'Flameeyes' Pettenò
2005-05-23 18:29 ` Mike Frysinger
2005-05-27 0:02 ` Diego 'Flameeyes' Pettenò
2005-05-27 13:44 ` Chris Gianelloni [this message]
2005-05-27 13:45 ` Diego 'Flameeyes' Pettenò
2005-05-27 14:04 ` Chris Gianelloni
2005-05-27 15:11 ` Mike Frysinger
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=1117201469.14290.232.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@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