| 1 |
On Thu, 2001-12-13 at 15:20, Mikael Hallendal wrote: |
| 2 |
> ons 2001-12-12 klockan 17.27 skrev Vitaly Kushneriuk: |
| 3 |
> > libgd-1.8.3-r2 needs freetype-1.3.1 and will not compile with |
| 4 |
> > freetype-2.0.5 |
| 5 |
> > they use different directories and install different libraries: |
| 6 |
> > /usr/include/freetype /usr/include/freetype2/freetype |
| 7 |
> > /usr/lib/libttf.* /usr/lib/libfreetype.* |
| 8 |
> > IMHO freetype-2.0.5 should be called freetype2-2.0.5, as this is a |
| 9 |
> > different package |
| 10 |
> |
| 11 |
> It is not a different package, just a newer version of a package which |
| 12 |
> happends to be incompatible with the previous version. |
| 13 |
> |
| 14 |
> The reason they are installing in /usr/include/freetype and |
| 15 |
> /usr/include/freetype2 is because the user should be able to have them |
| 16 |
> both installed at the same time. |
| 17 |
By the same reason, it should be named freetype-1... and freetype2-2.... |
| 18 |
So that freetype-1 will not be unmerged when installing freetype-2, |
| 19 |
when/if, we add auto-unmerge option to oprtage, etc. or interfere in |
| 20 |
some other way. |
| 21 |
Adding lib main version to the package name is the standard way of |
| 22 |
dealing with incompatible lib version, so that they can be |
| 23 |
installed/removed separately. |
| 24 |
|
| 25 |
> |
| 26 |
> This should be fixed by having dependencies like |
| 27 |
> freetype >= 1.3, < 2.0 (or whatever syntax we came up with). I'm not |
| 28 |
> sure of the current status of that. |
| 29 |
> |
| 30 |
> Regards, |
| 31 |
> Mikael Hallendal |
| 32 |
> |
| 33 |
> -- |
| 34 |
> |
| 35 |
> Mikael Hallendal |
| 36 |
> Gentoo Linux Developer, Desktop Team Leader |
| 37 |
> CodeFactory AB, Stockholm, Sweden |
| 38 |
> |
Archives