| 1 |
Apparently, though unproven, at 12:57 on Saturday 21 August 2010, Dale did |
| 2 |
opine thusly: |
| 3 |
|
| 4 |
> Hi, |
| 5 |
> |
| 6 |
> I'm wanting to install the latest KDE 4.5 which is in the kde overlay. |
| 7 |
> I got everything unmasked, keyworded and ready to go. Since this is a |
| 8 |
> large upgrade and will take some time to compile, I would like to just |
| 9 |
> build the binaries then come back and install them when the compiling is |
| 10 |
> all done. The emerge man page says this: |
| 11 |
> |
| 12 |
> --buildpkgonly (-B) |
| 13 |
> Creates binary packages for all ebuilds processed without actually |
| 14 |
> merging the packages. This comes with the caveat that all build-time |
| 15 |
> dependencies must already be emerged on the system. |
| 16 |
> |
| 17 |
> The part that I have a question on is the dependencies. Will portage be |
| 18 |
> able to build all the packages when the previous packages are not |
| 19 |
> installed yet? My thinking says this won't work but looking for a |
| 20 |
> second opinion from a more "seasoned" guru. |
| 21 |
|
| 22 |
|
| 23 |
Here's excellent advice: |
| 24 |
|
| 25 |
Do not install KDE-4.5 yet |
| 26 |
|
| 27 |
wait for 4.5.1 |
| 28 |
|
| 29 |
First, it's in an overlay, so when 4.5 hits the tree you will unmerge the |
| 30 |
whole lot again and redo it. How many spare cycles you got? |
| 31 |
|
| 32 |
If you have 4.4.5 installed from portage you will likely hit clashes with the |
| 33 |
overlay. There's were never pleasant in the 4.[23] era, I don't see that |
| 34 |
changing. |
| 35 |
|
| 36 |
4.5.0 has some pretty severe regressions, bad enough for QA to not put it in |
| 37 |
the tree |
| 38 |
|
| 39 |
4.5.0 does not have the kdepim suite - this might not apply to you. I can just |
| 40 |
imagine the akonadi updates when 4.5.1 hits the tree.... |
| 41 |
|
| 42 |
You gotta ask yourself "Is there a COMPELLING need for 4.5.0 other than it's |
| 43 |
brand new and shiny?" |
| 44 |
|
| 45 |
-- |
| 46 |
alan dot mckinnon at gmail dot com |
Archives