1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Thursday 05 February 2004 02:27, Spider wrote: |
5 |
> okay, |
6 |
> heres a juicy little thing with packages that depend (RDEPEND too) |
7 |
> on openssl. |
8 |
> |
9 |
> If an old system (openssl 0.9.6) installs said packages, we have a |
10 |
> working satisfied openssl install. However, this will fail miserably |
11 |
> once installed, since the packages themselves actually link to |
12 |
> libssl.so.0.9.7 and libcrypto.so.0.9.7. |
13 |
> |
14 |
> So, is there any way to make this behaviour work "better" with Gentoo? |
15 |
> The way that strikes me is to do it like RPM does, list library links |
16 |
> and depend on those files specifically. "foo won't install because |
17 |
> it depends on /usr/lib/libssl.so.7 which is not present" |
18 |
> |
19 |
> However, this is bad and broken behaviour as we just get one headache |
20 |
> for another ( what package supplies -that- .so file then? which of |
21 |
> theese 6000 packages is it I haven't installed? and with what USE flag |
22 |
> combination? ) |
23 |
> |
24 |
> so... |
25 |
> How can this sort of thing be dealt with? |
26 |
|
27 |
What we would want is compile-time dependencies. In such a case we can |
28 |
say, this package has been compiled with version X of that dependency, |
29 |
that version has SLOT Y. When we record such data, we can say that the |
30 |
SLOT's mismatch and find that the package has unfullfilled dependencies. |
31 |
|
32 |
It is probably sensible in any case to record/use this data. |
33 |
|
34 |
Paul |
35 |
|
36 |
- -- |
37 |
Paul de Vrieze |
38 |
Gentoo Developer |
39 |
Mail: pauldv@g.o |
40 |
Homepage: http://www.devrieze.net |
41 |
-----BEGIN PGP SIGNATURE----- |
42 |
Version: GnuPG v1.2.4 (GNU/Linux) |
43 |
|
44 |
iD8DBQFAIhL+bKx5DBjWFdsRAmE4AKDjVxIWiP9KL1EXh1FWF8ALQZKUnQCfa9ng |
45 |
ELmKGelxLpzznejXGj4dsW4= |
46 |
=wqo+ |
47 |
-----END PGP SIGNATURE----- |
48 |
|
49 |
-- |
50 |
gentoo-dev@g.o mailing list |