* [gentoo-amd64] Dropping qt-3
@ 2009-10-02 16:18 Mark Haney
2009-10-02 16:25 ` [gentoo-amd64] " Nikos Chantziaras
2009-10-02 16:29 ` [gentoo-amd64] " Gennady Tsoy
0 siblings, 2 replies; 4+ messages in thread
From: Mark Haney @ 2009-10-02 16:18 UTC (permalink / raw
To: gentoo-amd64
I'm a little curious. I've got two versions of QT (3 & 4) on my system.
That's not a problem as I have multiple python versions too. What I"m
curious about is when will it (or is it) safe to unmerge qt3?
--
Non curo. Si metrum non habet, non est poema.
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
^ permalink raw reply [flat|nested] 4+ messages in thread
* [gentoo-amd64] Re: Dropping qt-3
2009-10-02 16:18 [gentoo-amd64] Dropping qt-3 Mark Haney
@ 2009-10-02 16:25 ` Nikos Chantziaras
2009-10-02 16:29 ` [gentoo-amd64] " Gennady Tsoy
1 sibling, 0 replies; 4+ messages in thread
From: Nikos Chantziaras @ 2009-10-02 16:25 UTC (permalink / raw
To: gentoo-amd64
On 10/02/2009 07:18 PM, Mark Haney wrote:
> I'm a little curious. I've got two versions of QT (3& 4) on my system.
> That's not a problem as I have multiple python versions too. What I"m
> curious about is when will it (or is it) safe to unmerge qt3?
It's not a system package so you can remove it whenever you want without
any ill consequences. If something else needs it, it will pull it back
automatically.
To save you a needless rebuild in case something pulls it back, the best
way to know is to simply remove all instances of x11-libs/qt* from
/var/lib/portage/world (if it's there) and then run "emerge -a
--depclean". This will remove it if it's no longer needed.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-amd64] Dropping qt-3
2009-10-02 16:18 [gentoo-amd64] Dropping qt-3 Mark Haney
2009-10-02 16:25 ` [gentoo-amd64] " Nikos Chantziaras
@ 2009-10-02 16:29 ` Gennady Tsoy
1 sibling, 0 replies; 4+ messages in thread
From: Gennady Tsoy @ 2009-10-02 16:29 UTC (permalink / raw
To: gentoo-amd64
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
It is safe to unmerge qt3 while you are not using any application depends on
it.
On Fri, Oct 2, 2009 at 8:18 PM, Mark Haney <mhaney@ercbroadband.org> wrote:
> I'm a little curious. I've got two versions of QT (3 & 4) on my system.
> That's not a problem as I have multiple python versions too. What I"m
> curious about is when will it (or is it) safe to unmerge qt3?
>
> --
> Non curo. Si metrum non habet, non est poema.
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
>
[-- Attachment #2: Type: text/html, Size: 830 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-amd64] Dropping qt-3
@ 2009-10-02 16:45 Dmitri Pogosyan
0 siblings, 0 replies; 4+ messages in thread
From: Dmitri Pogosyan @ 2009-10-02 16:45 UTC (permalink / raw
To: gentoo-amd64
Do
equery depends qt
and see how many packages depend on qt3 (=x11-libs/qt-3). Mainly, it is
kde-3.5 that has to have qt3. If the dependence is conditional on qt3, then
you can avoid it buy recompiling the package with USE='-qt3'
> I'm a little curious. I've got two versions of QT (3 & 4) on my system.
> That's not a problem as I have multiple python versions too. What I"m
> curious about is when will it (or is it) safe to unmerge qt3?
>
> --
> Non curo. Si metrum non habet, non est poema.
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
--
Dmitri Pogosyan Department of Physics
Professor University of Alberta
tel 1-780-492-2150 11322 - 89 Avenue
fax 1-780-492-0714 Edmonton, AB, T6G 2G7, CANADA
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-10-02 16:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-02 16:18 [gentoo-amd64] Dropping qt-3 Mark Haney
2009-10-02 16:25 ` [gentoo-amd64] " Nikos Chantziaras
2009-10-02 16:29 ` [gentoo-amd64] " Gennady Tsoy
-- strict thread matches above, loose matches on Subject: below --
2009-10-02 16:45 Dmitri Pogosyan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox