Alex Schuster wrote:
Dale writes:
I'm wanting to install the latest KDE 4.5 which is in the kde overlay.
I got everything unmasked, keyworded and ready to go. Since this is a
large upgrade and will take some time to compile, I would like to just
build the binaries then come back and install them when the compiling
is all done. The emerge man page says this:
--buildpkgonly (-B)
Creates binary packages for all ebuilds processed without actually
merging the packages. This comes with the caveat that all
build-time dependencies must already be emerged on the system.
The part that I have a question on is the dependencies. Will portage
be able to build all the packages when the previous packages are not
installed yet? My thinking says this won't work but looking for a
second opinion from a more "seasoned" guru.
I'm no guru, but I'm very sure it won't work.
You could do this on a second machine, or in a chroot, or in a virtual
machine, and then distribute the binary packages. Which would be quite
some additional work.
I'm running KDe 4.5, and it works fine. That is, there are fewer new bugs
for me than were fixed.
Wonko
Well, I bit the bullet and hit Y. This is what portage told me:
Would you like to merge these packages? [Yes/No] y
!!! --buildpkgonly requires all dependencies to be merged.
!!! Cannot merge requested packages. Merge deps and try again.
r...@smoker / #
You're right. It ain't going to work. Now we know.
Thinking about copying my install to a second drive and installing it
there. I can do it in a chroot and have a fall back install in case it
borks, pukes or has some other kind of failure. I might add, it puked
yesterday. I had no GUI for a while. It even killed kdm. I had to
unmerge some packages to get rid of blocks then revert back to the old
stable KDE to get a GUI.
Yea, the keyboard was working and this was not hal related. lol I just
wanted to get that out of the way before things got out of hand. ;-)
Dale
:-) :-)
