1 |
On Fri, 29 May 2015 18:48:55 -0700 walt wrote: |
2 |
> <gory details of many frustrating hours of fighting with one particular |
3 |
> gentoo package have been snipped to eliminate uncouth language> |
4 |
> |
5 |
> I think of a gentoo "binary" package (e.g. oracle-jdk-bin) as an ebuild |
6 |
> that fetches a file from somewhere, then merely unpacks that file and |
7 |
> sticks the results in /opt/<whatever>. |
8 |
> |
9 |
> My experience today with libreoffice-bin has broken my mental model of |
10 |
> how a gentoo "binary" package behaves. |
11 |
> |
12 |
> While trying to debug some broken behavior in the (non-binary) localc |
13 |
> spreadsheet app, I decided to install libreoffice-bin as an experiment. |
14 |
> |
15 |
> The libreoffice-bin package wanted to drag in dozens of other non-binary |
16 |
> gentoo packages before it would install itself, and even caused a blocker |
17 |
> between two different versions of poppler. (I said "no" because I thought |
18 |
> the blocker would make the entire experiment fail in the end.) |
19 |
|
20 |
It requires many other packages because it was compiled with |
21 |
specific versions of that packages. Of course that other packages |
22 |
will be source ebuilds mostly. |
23 |
|
24 |
You have blockers because your current system have different |
25 |
versions of some of that packages. These issues are usually solved |
26 |
either via slot installs or update of your currently installed |
27 |
system. Sometimes emerge -DNu @world may be needed. |
28 |
|
29 |
As for terminology, there are two kinds of binary packages: |
30 |
1) binpkg — (usually) user-build binary packages, just a tarballs |
31 |
of source build packages. They are usufull for clustering, fast |
32 |
deployment, fast downgrades and so on. |
33 |
2) The same binpkg packages, but put into the portage tree for |
34 |
specific "hard to build" packages, they usually have "-bin" suffix. |
35 |
That is your case. |
36 |
|
37 |
Best regards, |
38 |
Andrew Savchenko |