| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 13/05/14 03:19 PM, Pacho Ramos wrote: |
| 5 |
> El dom, 11-05-2014 a las 20:56 +0200, Michał Górny escribió: [...] |
| 6 |
>> 4. whenever possible, depend on the specific subslot that is |
| 7 |
>> known to provide SONAME equal to the required by your package, |
| 8 |
>> e.g. for libgcrypt.so.20 you depend on libgcrypt:0/20, |
| 9 |
> [...] |
| 10 |
> |
| 11 |
> Why is this needed? Thanks for the explanation :) |
| 12 |
> |
| 13 |
> |
| 14 |
|
| 15 |
I believe that this relates to cases of, by example, a 32bit |
| 16 |
pre-rolled binary package on amd64. I expect one could use a specific |
| 17 |
version range (upper/lower) for the dependency instead, so long as it |
| 18 |
is just as accurate. |
| 19 |
-----BEGIN PGP SIGNATURE----- |
| 20 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 21 |
|
| 22 |
iF4EAREIAAYFAlNycTQACgkQ2ugaI38ACPBswQEAugV6KeFBCPz30cBLeG7Ebsnn |
| 23 |
Y0C8E4bG1WxSY5JNSfIA/2vEMZPdcbFMnfpHI0AEqvo7YkreXzvvo+oE6t0mlrI/ |
| 24 |
=W3gq |
| 25 |
-----END PGP SIGNATURE----- |
Archives