| 1 |
On Tue, 2007-01-30 at 06:27 +0000, Ciaran McCreesh wrote: |
| 2 |
> [ Background: tr1 is a set of extensions to the C++ Standard Library |
| 3 |
> giving various useful things like hash tables and smart pointers. There |
| 4 |
> are partial implementations included in g++-4.1 and boost and full |
| 5 |
> implementations available from Dinkumware. It is likely that a lot of |
| 6 |
> C++ apps will start using it in the not too distant future. ] |
| 7 |
> |
| 8 |
> What is the best way to handle packages that require parts of tr1? The |
| 9 |
> options appear to be: |
| 10 |
> |
| 11 |
> * Hard dep upon boost. This sucks for g++-4.1 users. |
| 12 |
> |
| 13 |
> * Hard dep upon g++-4.1, which isn't available for all archs. This |
| 14 |
> doesn't even work because there's no guarantee that >=4.1 is being used |
| 15 |
> even if it's installed. |
| 16 |
|
| 17 |
isn't it possible to check the version of gcc that is in _use_ in an |
| 18 |
ebuild, like i can do in a configure script? if so, one could provide a |
| 19 |
"old-gcc" use flag that must be enabled when trying to build with |
| 20 |
<gcc-4.1.0 (that actually pulls in boost etc.) and must not be enabled |
| 21 |
when using >=gcc-4.1.0 ... |
| 22 |
|
| 23 |
> |
| 24 |
> * || ( ) deps, and hope that if the user has 4.1 installed then they're |
| 25 |
> using it. Since library implementations aren't runtime switchable, this |
| 26 |
> will lead to breakages if users upgrade gcc and then remove boost. |
| 27 |
> |
| 28 |
|
| 29 |
switching gcc versions may lead to breakage anyway if the user doesn't |
| 30 |
know what he/she is doing. |
| 31 |
|
| 32 |
> None of these are particularly nice... |
| 33 |
> |
| 34 |
|
| 35 |
nope ... let's hope c++-0x comes out soon and that compiler vendors are |
| 36 |
faster in implementing it than c++-98. |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives