From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] virtual/eject ?
Date: Fri, 27 May 2005 10:04:32 -0400 [thread overview]
Message-ID: <1117202672.14290.236.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <200505271546.01534@enterprise.flameeyes.is-a-geek.org>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
On Fri, 2005-05-27 at 15:45 +0200, Diego 'Flameeyes' Pettenò wrote:
> On Friday 27 May 2005 15:44, Chris Gianelloni wrote:
> > I'm just curious, but why exactly is a virtual needed?
> Well there are nine packages (and probably there can be others) which needs
> eject, and the eject commands are going to be quite a few if there isn't an
> "universal" eject as every os has its own way to eject a CD-Rom.
> So we'll have eject for linux, eject-bsd for freebsd (and maybe openbsd, don't
> know), eject-osx (and maybe eject-darwin) and eventual eject-solaris if there
> will ever be a solaris port.
> Every kernel has its own syscalls, and using conditional deps for every kernel
> on more than a couple of packages will surely be something annoying for
> maintainers.
OK... You sold me.
So create a virtual/eject... =]
--
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 14:05 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
2005-05-27 13:45 ` Diego 'Flameeyes' Pettenò
2005-05-27 14:04 ` Chris Gianelloni [this message]
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=1117202672.14290.236.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