Emerge - check if package is installed
Hello,
I have installed Qt 4.7.2 manually yesterday, but when I want to install some other applications or libs, emerge always want me to install qt-core. (of older version). Is there any way to make emerge consider qt as installed? or just to check some path and actually find, that it is installed. Thanks |
Quote:
|
I've got very slow and limited internet connection here (on target computer), so I downloaded qt, KDE, and everything bigger from the other place. (I was also looking for some Linux software dvds, but that's different topic.)
|
If you need to download from another machine you can get the files from ftp://ftp.osuosl.org/pub/gentoo/distfiles/ or whatever mirror you choose.
For example, for qt ftp://ftp.osuosl.org/pub/gentoo/dist...c-4.7.2.tar.gz Then, put it in /usr/portage/distfiles/ |
Thanks,
I already figured that out myself, but I was interested if it's not possible to do the thing I mentioned before. I was introduced of portage as being highly configurable and advanced package manager, so I wonder where does it store informations about installed software and corresponding paths. |
The best way might be to create your own qt-core-4.7.2 and then install it with emerge.
|
Quote:
Code:
x11-libs/qt-core You can use this command to see the needed files: Code:
emerge -pf qt-core ---------- Post added 22nd Mar 2011 at 09:44 ---------- Quote:
|
Thanks for your answer,
what I tried to tell is that by the time I was trying to install Qt, I didn't know the possibility to download files from /distfiles/ directory on FTP server, so I decided to download Qt from it's official site, and install it by hand. |
I understood, but still it's not the cleanest way to do so in Gentoo. It's not only about portage being aware of the package you installed by hand, but also about the rest of your user land having to live with such software. Note that in most distros, leftovers from source/lib packages are not -potentially- as harmful as they are in Gentoo, being it a source based meta-distro. If you install qt-core by hand and you are not carefull enough to preserve the build tree (so you can make uninstall or similar) you will be leaving bits and pieces behind each time you upgrade qt-core, or whenever you decide to go from your manually installed qt-core to the portage one.
One day you might be wondering why package-X doesn't compile against your newly installed qt-core version that it requires when it's really trying to compile and/or link against the old pieces lying around in your system. And compilation errors are -usually- explicit enough and easy to diagnose, but there are some more obscure things that can happen and that are harder to diagnose, requiring to dive into strace, dbg or similar tools to find what is causing some odd runtime error on something that should just work. |
Thanks for explanation,
I'm already using portage's one, and understand the reasons. As I said that time I was (I thought I was) forced to do that, because I didn't know about availability of files through FTP, and had slow internet connection. |
All times are GMT -5. The time now is 09:16 PM. |