| 1 |
On Thu, Jan 28, 2010 at 04:17:41PM +0100, Beber wrote: |
| 2 |
> So, I did a wrapper to emerge --buildpkg to create tbz2 with SHA1 in |
| 3 |
> names function of USE, like : |
| 4 |
> CHOST="x86_64-pc-linux-gnu" |
| 5 |
> ACCEPT_KEYWORDS="amd64" |
| 6 |
> tcpdump |
| 7 |
> |
| 8 |
> USE="+chroot +ipv6 -ssl -test -samba -smi" |
| 9 |
> is placed under /data/pkg/amd64/x86_64-pc-linux-gnu/net-analyzer/tcpdump-4.0.1_pre20090709+2bf4bfffad82d4ae519f76770b4f7db7b4416738.tbz2 |
| 10 |
> |
| 11 |
> USE="+chroot +ipv6 +ssl -test +samba -smi" |
| 12 |
> is placed under /data/pkg/amd64/x86_64-pc-linux-gnu/net-analyzer/tcpdump-4.0.1_pre20090709+5e099e8337e4cadfceda6ccf4c881fbb495980bd.tbz2 |
| 13 |
A word of warning on this. |
| 14 |
|
| 15 |
Simply capturing the USE flags is not enough, the libraries that a |
| 16 |
binary is linked against can cause problems as well, as the dependency |
| 17 |
imposed by linking is much stricter than the RDEPEND in the ebuild. |
| 18 |
|
| 19 |
tcpdump for example has: |
| 20 |
RDEPEND="... ssl? ( >=dev-libs/openssl-0.9.6m )" |
| 21 |
|
| 22 |
But if you built and linked against openssl-0.9.7*, then upgraded to |
| 23 |
openssl-0.9.8, you can expect breakage. |
| 24 |
|
| 25 |
Similar things happened with binaries linked against libmysqlclient in |
| 26 |
the past. |
| 27 |
|
| 28 |
As to my own take on a solution to the problem for work stuff, we simply |
| 29 |
maintain one chroot per unique environment (we only have 5 envs), and |
| 30 |
build in the chroot, then use those binpkgs on the boxes. |
| 31 |
|
| 32 |
-- |
| 33 |
Robin Hugh Johnson |
| 34 |
Gentoo Linux: Developer, Trustee & Infrastructure Lead |
| 35 |
E-Mail : robbat2@g.o |
| 36 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives