From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage problem
Date: Fri, 14 Mar 2008 23:25:28 +0200 [thread overview]
Message-ID: <200803142325.29095.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <47DAC985.9020907@chuckr.org>
On Friday 14 March 2008, Chuck Robey wrote:
> Vladimir Rusinov wrote:
> > Just add opengl to your use flags and `emerge -v1 =x11-libs/qt-3*`
> > Then, you'll probably need `emerge --update --deep --newuse
> > kde-meta` (or emerge -uDN kde-meta)
>
> You aren't understanding me. I am fully aware of qt versions 3 and
> 4, and if I was gbuilding them on my own, this wouldn't be a problem,
> but I am trying to use the portage system, and there isnt'any such
> emerge package named like this, at least, none I can find, none
> 'emerge -s qt-3*' could find either. If you could identify for me
> what the heck the real package name is, I would gladly rebuild it.
> I'm not having trouble with the command line, I'm having trouble
> finding the cirrect thing to rebuild.
qt is SLOTted, I think you are simply using the wrong syntax. Using my
machine as an example (you should also emerge eix, it's so much easier
and quicker than emerge -s):
alan@nazgul ~/bin $ eix -e qt
[I] x11-libs/qt
Available versions:
(3) 3.3.4-r8 3.3.8-r4
(4) 4.3.2-r1 (~)4.3.3 (~)4.3.4 [M](~)4.4.0_beta1
The SLOTs are "3" and "4"
If I try to update qt, portage will update qt4 as it's the latest
version. I would have to do something like
emerge =qt-3.3.8-r4
or the newish syntax incorporating SLOTs
emerge qt:3
You were essentially trying to tell portage to update a package
called "qt-3", there is no such package. And getting to grips with
emerge's version number syntax can be a bitch
Does this answer your query?
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-14 21:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 17:58 [gentoo-user] portage problem Chuck Robey
2008-03-14 18:11 ` Vladimir Rusinov
2008-03-14 18:52 ` Chuck Robey
2008-03-14 19:06 ` Chris Brennan
2008-03-14 21:25 ` Alan McKinnon [this message]
2008-03-15 15:59 ` Chuck Robey
2008-03-14 21:50 ` Neil Bothwick
2008-03-15 16:02 ` Chuck Robey
2008-03-15 18:08 ` Dale
2008-03-15 18:10 ` Chuck Robey
2008-03-15 18:30 ` Dale
2008-03-15 19:22 ` Uwe Thiem
2008-03-15 16:13 ` Chuck Robey
2008-03-15 21:47 ` Neil Bothwick
2008-03-15 22:54 ` Chuck Robey
2008-03-16 1:51 ` Chuck Robey
2008-03-16 8:32 ` Neil Bothwick
2008-03-16 17:31 ` Chuck Robey
2008-03-16 17:47 ` Neil Bothwick
2008-03-16 10:07 ` Alan McKinnon
2008-03-16 10:25 ` Dale
2008-03-16 17:43 ` Chuck Robey
2008-03-16 18:55 ` Alan McKinnon
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 21:47 [gentoo-user] Portage Problem Timothy A. Holmes
2006-03-14 23:38 ` Patrick Börjesson
[not found] <5Q29C-1AD-5@gated-at.bofh.it>
[not found] ` <5Q2VN-2LY-3@gated-at.bofh.it>
2006-03-14 8:16 ` [gentoo-user] portage problem Martin Gysel
2006-03-13 20:40 Martin Gysel
2006-03-13 21:36 ` Zac Medico
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=200803142325.29095.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--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