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]  Re: realplayer download security problem
Date: Tue, 15 Nov 2005 23:15:02 +0100	[thread overview]
Message-ID: <437A5DE6.5090300@planet.nl> (raw)
In-Reply-To: <loom.20051115T220716-80@post.gmane.org>

James schreef:
> How does a gentoo system know the difference between an rpm file that
> it can install  and a rpm file that it cannot or should not install
> on a gentoo system?
> 

It's not like RPMs (or DEBs for that matter) just *appear* on the system
and are installed by mental telepathy.... if you emerge an ebuild for
which the package file is an RPM (RealPlayer and the ATI proprietary
drivers are two which come to mind), then that is what will be installed.

The Portage system knows what files are available to it, because that's
what the Portage tree is for. For example, the Cedega binary package is
available as an RPM, a DEB amd a TGZ-- but if you attempt to install it
(it's a fetch-restricted package, which requires subscription to
download, so you have to download it and put it in
/usr/portage/distfiles yourself by default) it's not like Portage wants
any of the three. It wants specifically the -small.tgz, and you could
put the RPM in distfiles if you wanted, but Portage wouldn't install it.
Because that's not the package that the ebuild specifies.

Of course, you could install rpm and install any rpm you wanted with
it-- but since you don't have an RPM database, and even if you did, all
the dependent libraries and system files wouldn't be in it (because they
were not installed from RPM), it would be likely to end in tears (which
would be no less than one deserved, since if one wanted to use RPMs so
bad, one should have installed a binary distro that depends on them and
not a source-based distro like this one :-) ).

In any case, the relatively few RPMs in the Portage tree are generally
there (afaik), because we don't get a choice about it-- the binaries
provided (usually by some proprietary source) are only packaged *as*
RPMs, so if we want or need them, that's what we have to use. Certainly
that is the case for the ATI drivers, and likely for the RealPlayer
package as well.

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



  reply	other threads:[~2005-11-15 22:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 17:29 [gentoo-user] realplayer download security problem James
2005-11-15 17:50 ` Lucien D.
2005-11-15 21:06   ` [gentoo-user] Solved: " James
2005-11-15 18:08 ` [gentoo-user] " Catalin Trifu
2005-11-15 18:12 ` Rumen Yotov
2005-11-15 19:26   ` [gentoo-user] " James
2005-11-15 20:41     ` Nick Rout
2005-11-15 21:11       ` James
2005-11-15 22:15         ` Holly Bostick [this message]
2005-11-15 22:47           ` Nick Rout
2005-11-15 23:14             ` Holly Bostick
2005-11-15 23:35               ` Nick Rout
2005-11-16  1:42               ` James
2005-11-15 22:35         ` Nick Rout

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=437A5DE6.5090300@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