| 1 |
Dale writes: |
| 2 |
|
| 3 |
> I'm wanting to install the latest KDE 4.5 which is in the kde overlay. |
| 4 |
> I got everything unmasked, keyworded and ready to go. Since this is a |
| 5 |
> large upgrade and will take some time to compile, I would like to just |
| 6 |
> build the binaries then come back and install them when the compiling |
| 7 |
> is all done. The emerge man page says this: |
| 8 |
> |
| 9 |
> --buildpkgonly (-B) |
| 10 |
> Creates binary packages for all ebuilds processed without actually |
| 11 |
> merging the packages. This comes with the caveat that all |
| 12 |
> build-time dependencies must already be emerged on the system. |
| 13 |
> |
| 14 |
> The part that I have a question on is the dependencies. Will portage |
| 15 |
> be able to build all the packages when the previous packages are not |
| 16 |
> installed yet? My thinking says this won't work but looking for a |
| 17 |
> second opinion from a more "seasoned" guru. |
| 18 |
|
| 19 |
I'm no guru, but I'm very sure it won't work. |
| 20 |
|
| 21 |
You could do this on a second machine, or in a chroot, or in a virtual |
| 22 |
machine, and then distribute the binary packages. Which would be quite |
| 23 |
some additional work. |
| 24 |
|
| 25 |
I'm running KDe 4.5, and it works fine. That is, there are fewer new bugs |
| 26 |
for me than were fixed. |
| 27 |
|
| 28 |
Wonko |
Archives