| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 18/12/13 01:10 PM, Anthony G. Basile wrote: |
| 5 |
> On 12/18/2013 02:54 AM, Michał Górny wrote: |
| 6 |
>> |
| 7 |
>> The problem with this solution is that as soon as user upgrades, |
| 8 |
>> shklee is forced to use C++11. On the other hand, we get rid of |
| 9 |
>> pre-C++11 packages quite transparently, without extra work. |
| 10 |
>> |
| 11 |
>> |
| 12 |
>> What are your thoughts? |
| 13 |
>> |
| 14 |
> I assume with variant a you will be able to go back and forth |
| 15 |
> between C++11 abi and pre-C++11. If so, please adopt variant a. |
| 16 |
> |
| 17 |
|
| 18 |
It would, but unless it's done in a way similar to multilib's |
| 19 |
abi_{x86,amd64,x32} (as was mentioned in the "crazy idea" post), only |
| 20 |
one version would be installed at a time. |
| 21 |
|
| 22 |
(that is, unless I misread the original proposal and both a generic |
| 23 |
and a c++11 version would be installed if the flag was enabled -- i |
| 24 |
can see the utility to that solution, but I am not a fan of it; better |
| 25 |
to convert and patch when it becomes necessary) |
| 26 |
|
| 27 |
-----BEGIN PGP SIGNATURE----- |
| 28 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 29 |
|
| 30 |
iF4EAREIAAYFAlKx6UwACgkQ2ugaI38ACPC26wD/cS7sN4eK67blugKVq/fUDbEv |
| 31 |
50PtDy8xdgBp0tFowZwA/3GrPaROmN5XOUf8nW1tuoeuoD5oVH3nIGV/5AotXSZR |
| 32 |
=FkC9 |
| 33 |
-----END PGP SIGNATURE----- |
Archives