1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 17/06/12 11:53 AM, Michał Górny wrote: |
5 |
> On Sun, 17 Jun 2012 17:46:00 +0200 Thomas Sachau <tommy@g.o> |
6 |
> wrote: |
7 |
>>> |
8 |
>>> ... If I weren't using 32-bit libs, and now I want to compile |
9 |
>>> 32-bit wine, I have to recompile most of my libraries for both |
10 |
>>> ABIs. That is a no go for me. |
11 |
>> |
12 |
>> So you want to build a 32bit package, which is depending on |
13 |
>> 32bit libs, but want to do that without the needed dependencies? |
14 |
>> Please tell me, how that works. |
15 |
> |
16 |
> I'm trying to build a 32bit package and its 32bit dependencies. |
17 |
> Your solution involves building a 32bit package and rebuilding all |
18 |
> 64bit packages which happen to be its dependencies for no reason. |
19 |
|
20 |
Wait, so a package will be re-emerged but only for the new ABI? So |
21 |
we're looking at partial package installing now? |
22 |
|
23 |
Or is this going to make multi-ABI installs be more like the way |
24 |
crossdev works, where each individual package supporting multiple ABIs |
25 |
will be installed multiple times, independently? |
26 |
|
27 |
-----BEGIN PGP SIGNATURE----- |
28 |
Version: GnuPG v2.0.17 (GNU/Linux) |
29 |
|
30 |
iF4EAREIAAYFAk/fQAEACgkQ2ugaI38ACPCtFwD7BzuNxk00HgBfK5zd9dOwhcPw |
31 |
YJVvpXZR0AXtQyx46RQA/jR8Uqv1T99Tc+vhMWsGHLzfMDRR2DU8FlSFswQ2PG11 |
32 |
=eeDE |
33 |
-----END PGP SIGNATURE----- |