| 1 |
2015-04-24 21:56 GMT+03:00 Ian Stakenvicius <axs@g.o>: |
| 2 |
|
| 3 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
> Hash: SHA256 |
| 5 |
> |
| 6 |
> On 24/04/15 02:42 PM, Ciaran McCreesh wrote: |
| 7 |
> > On Fri, 24 Apr 2015 21:12:32 +0300 Maxim Koltsov |
| 8 |
> > <maksbotan@g.o> wrote: |
| 9 |
> >> Hello. My previous email was sent from the wrong address and it |
| 10 |
> >> seems it did not make it into the list. Sending again from the |
| 11 |
> >> right address... |
| 12 |
> >> |
| 13 |
> >> I'm introducing "c++14" use flag to every package in |
| 14 |
> >> app-leechcraft catherogy via leechcraft.eclass. I need to put USE |
| 15 |
> >> description somewhere. I propose / ask for permission to do it in |
| 16 |
> >> global use.desc. Putting this flag to every single metadata.xml |
| 17 |
> >> feels just wrong --- there are 72 of them now. |
| 18 |
> >> |
| 19 |
> >> Proposed description: "Build using C++ 14 standard" |
| 20 |
> >> |
| 21 |
> >> Looking forward for comments. |
| 22 |
> > |
| 23 |
> > This isn't going to be sustainable... What's the long-term plan |
| 24 |
> > for dealing with this? |
| 25 |
> > |
| 26 |
> |
| 27 |
> Sounds like we need to go through the archives and revisit the |
| 28 |
> conversations about how to integrate c++11 , again.. |
| 29 |
> |
| 30 |
> This is temporal, until gcc gets needed support and that version makes its |
| 31 |
way into ~. Then the flag won't be needed anymore, we'll just depend on new |
| 32 |
enough gcc and enable C++14 mode by default. |
| 33 |
|
| 34 |
I'm CCing LeechCraft author just in case. |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
> -----BEGIN PGP SIGNATURE----- |
| 39 |
> Version: GnuPG v2 |
| 40 |
> |
| 41 |
> iF4EAREIAAYFAlU6kfYACgkQ2ugaI38ACPCDuQEAhAv0boCkTU3RvT5d/fX3la7V |
| 42 |
> 8so0wqnPtHKI4fSqEwgA+wXmVlB14ykbTQ1VnrRR5WrEPRjMbm9V1MSXAA6MnC43 |
| 43 |
> =i/3U |
| 44 |
> -----END PGP SIGNATURE----- |
| 45 |
> |
| 46 |
> |
Archives