| 1 |
El mar, 13-05-2014 a las 15:23 -0400, Ian Stakenvicius escribió: |
| 2 |
> On 13/05/14 03:19 PM, Pacho Ramos wrote: |
| 3 |
> > El dom, 11-05-2014 a las 20:56 +0200, Michał Górny escribió: [...] |
| 4 |
> >> 4. whenever possible, depend on the specific subslot that is |
| 5 |
> >> known to provide SONAME equal to the required by your package, |
| 6 |
> >> e.g. for libgcrypt.so.20 you depend on libgcrypt:0/20, |
| 7 |
> > [...] |
| 8 |
> > |
| 9 |
> > Why is this needed? Thanks for the explanation :) |
| 10 |
> > |
| 11 |
> > |
| 12 |
> |
| 13 |
> I believe that this relates to cases of, by example, a 32bit |
| 14 |
> pre-rolled binary package on amd64. I expect one could use a specific |
| 15 |
> version range (upper/lower) for the dependency instead, so long as it |
| 16 |
> is just as accurate. |
| 17 |
|
| 18 |
Ah, ok :) |
Archives