Are you refering to Gnome? as I don't see any downgrades
marked (they have a D there). If it's because the UI
needs that version of Gnome and will install it in a
different slot so it coexists with your current version
which appears to be 2.x.
On Thu, 7 Aug 2003 11:47:50 -0400 (EDT)
Jason
Hrm...What does the SLOT=1 in gnome-vfs-1.0.5-r3.ebuild mean? I'm still
a little new to gentoo. I've only be using it for a few months now.
Thanks!
--Jason
On Thu, 7 Aug 2003, brett holcomb wrote:
Yes, they will coexist. To check for sure look at the
ebuild for a SLOT= entry.
It
So they would coexist? It looks like it thinks that it will be
upgrading gconf from version 2.2.0 to 1.0.8-r5 which is clearly a
downgrade to me. Similar with gnome-vfs (upgraded from 2.2.4 to
1.0.5-r3). It would only put a D if it thinks it's a downgrade. In
this case, it thinks that
Hmmm...so it doesn't take the SLOT into account when it's determining if
something is an upgrade or an install? I guess that's why it thinks it's
upgrading from 2.2.0 to 1.0.5-r3 but it's really a new install.
Hmmm...interesting. I'm going to try and do an install of one of the
dependency
On 2003.08.07 11:47, Jason A. Pfeil wrote:
Does anyone know why whenever I want to install *any* of the xine GUIs
(oxine, gxine, xine-ui) it wants to downgrade me as follows?
running emerge -p gxine...
These are the packages that I would merge, in order:
Calculating dependencies ...done!
It means that this version will go in what it calls SLOT
1. It's a way for Gentoo to install different versions of
the same package such as Gnome. They coexist on the
system.
On Thu, 7 Aug 2003 12:07:02 -0400 (EDT)
Jason A. Pfeil [EMAIL PROTECTED] wrote:
Hrm...What does the SLOT=1 in
I understand. It was just a little confusing. Now I understand how it
works. I tried to manually install that version and it wouldn't let me.
I tried to emerge -u libglade and it said that there was no upgrade.
Then, I tried to emerge it and it wanted to re-merge the installed one.
Then
Totem gives me the same stuff. It looks like my xmms USE flag is messing
up the mix. Grrr...let me see if that's doing it.
--Jason
On Thu, 7 Aug 2003, Alan wrote:
On Thu, Aug 07, 2003 at 11:47:50AM -0400, Jason A. Pfeil wrote:
Does anyone know why whenever I want to install *any* of the
Thanks for the hint, Chris. I got it squared away already.
Thanks!
--Jason
On Thu, 7 Aug 2003, Chris I wrote:
On 2003.08.07 11:47, Jason A. Pfeil wrote:
Does anyone know why whenever I want to install *any* of the xine GUIs
(oxine, gxine, xine-ui) it wants to downgrade me as follows?
Does anyone know why whenever I want to install *any* of the xine GUIs
(oxine, gxine, xine-ui) it wants to downgrade me as follows?
running emerge -p gxine...
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N ] media-libs/libfame-0.9.0
On Thu, Aug 07, 2003 at 11:47:50AM -0400, Jason A. Pfeil wrote:
Does anyone know why whenever I want to install *any* of the xine GUIs
(oxine, gxine, xine-ui) it wants to downgrade me as follows?
[snip]
I'm not familiar with the frontends you're listing there, but have you
tried totem? It
begin quote
On Thu, 7 Aug 2003 18:40:02 -0400
Brett I. Holcomb [EMAIL PROTECTED] wrote:
As I understand it the ebuild will set conditions on what it needs to
have built (the dependencies). Just doing -u will say it has the
latest. To emerge previous versions you have to use the path
Hrm...I forgot about totem. Thanks. I'll look into that one.
--Jason
On Thu, 7 Aug 2003, Alan wrote:
On Thu, Aug 07, 2003 at 11:47:50AM -0400, Jason A. Pfeil wrote:
Does anyone know why whenever I want to install *any* of the xine GUIs
(oxine, gxine, xine-ui) it wants to downgrade me as
Hrm...removing xmms from my USE flags didn't get rid of totem wanting to
install it. Same for oxine, gxine, and xine-ui. Plus they want to
upgrade my xine-lib from 0.9.13-r3 to 1_beta12. Will xine-lib-1_beta12
work with the xine-d5d-0.2.7-r1 ebuild?
Thanks!
--Jason
On Thu, 7 Aug 2003,
it backwards.. Whatever is in the [] is what its upgrading TOO..So
gconf is going from 1.0.8-r5 TO 2.2.0
Thanks,
Jeff
-Original Message-
From: Jason A. Pfeil [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 10:59 AM
To: [EMAIL PROTECTED]
Subject: Re: [gentoo-user] xine
Yes, they will coexist. To check for sure look at the
ebuild for a SLOT= entry.
It might be your USE flags. If you hae gnome in it then
it will build it with gnome stuff enabled. Try adding
-gnome to the USE flag and see what happens.
On Thu, 7 Aug 2003 11:59:29 -0400 (EDT)
Jason A. Pfeil
Oh. I didn't realize that you could emerge a specific .ebuild file.
Hmmm...interesting. :-)
Thanks!
--Jason
On Thu, 7 Aug 2003, Brett I. Holcomb wrote:
As I understand it the ebuild will set conditions on what it needs to have
built (the dependencies). Just doing -u will say it has the
No, the [] is what you have.
On Thu, 7 Aug 2003 11:29:59 -0500
Jeffrey Smelser [EMAIL PROTECTED] wrote:
Your getting it backwards.. Whatever is in the [] is what
its upgrading TOO..So gconf is going from 1.0.8-r5 TO
2.2.0
Thanks,
Jeff
-Original Message-
From: Jason A. Pfeil
Well it does sort of. as far as it's concerned it's new or
an upgrade. If it didn't take into account the slot it
would say D for downgrade.
On Thu, 7 Aug 2003 12:28:26 -0400 (EDT)
Jason A. Pfeil [EMAIL PROTECTED] wrote:
Hmmm...so it doesn't take the SLOT into account when it's
determining
As I understand it the ebuild will set conditions on what it needs to have
built (the dependencies). Just doing -u will say it has the latest. To
emerge previous versions you have to use the path /usr/portage/... .
I understand. It was just a little confusing. Now I understand how it
20 matches
Mail list logo
