| 1 |
>>For example there are the gcc3.2/3.3 ebuilds, and the libstdc++-ebuild |
| 2 |
>>that supply the same libstdc++ versions. |
| 3 |
> |
| 4 |
> if they have the same name down to the version number, they are supposed to |
| 5 |
> binary compatible and i see no reason we should try to work around that |
| 6 |
|
| 7 |
Sorry, i think you misunderstood me. |
| 8 |
|
| 9 |
How would you modify the ebuild blackdown-jdk for example? It must |
| 10 |
express a dependency on gcc3.2/3.3's libstdc++, but it can't. There's no |
| 11 |
virtual for that yet. |
| 12 |
|
| 13 |
|
| 14 |
-- |
| 15 |
gentoo-dev@g.o mailing list |
Archives