| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Thursday 05 February 2004 19:25, Spider wrote: |
| 5 |
> > |
| 6 |
> > My guess is that the problem I just raised could be solved by adding |
| 7 |
> > a |
| 8 |
> > |
| 9 |
> > portage function that runs at install-time and can either relocate |
| 10 |
> > files or just cause the emerge to fail with a warning, whereas the |
| 11 |
> > general linking issue is going to require a great deal more thought. |
| 12 |
> |
| 13 |
> Very true and another headache. It somehow feels that we need a |
| 14 |
> thinker on how to deal with this. Anyone here who feels |
| 15 |
> exceptionally bright this afternoon? |
| 16 |
|
| 17 |
Basically a LIBVER variable could in this case be introduced by python |
| 18 |
that is set to say 2.3 an will let all binary packages fail which were |
| 19 |
build with a different LIBVER. |
| 20 |
|
| 21 |
Paul |
| 22 |
|
| 23 |
- -- |
| 24 |
Paul de Vrieze |
| 25 |
Gentoo Developer |
| 26 |
Mail: pauldv@g.o |
| 27 |
Homepage: http://www.devrieze.net |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 30 |
|
| 31 |
iD8DBQFAKKWMbKx5DBjWFdsRAmc3AJ9FUmkGAkuwfMAhprdjUXoA/VUzygCeOQEm |
| 32 |
XN4vvvWXGN3N/XGjFttctgU= |
| 33 |
=VdnO |
| 34 |
-----END PGP SIGNATURE----- |
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-dev@g.o mailing list |
Archives