Hello folks,
I apologize to everyone for sending this proposal before it was
finished. It was not voted on by the QA team hence it was not an
official proposal by the QA team. There was probably some
misunderstanding in communication.
After we finish the official draft and it is accepted by QA te
On Tue, Jul 31, 2018 at 12:03 PM Luca Barbato wrote:
> > As far as I know, the Rust ecosystem is largely bimodal: stuff is either
> > compatible with stable and later, or it works only on nightly. It seems
> > very rare that code is actually tied to a particular Rust release and
> does
> > not co
# Joonas Niilola (31 Jul 2018)
# Old and obsolete. Merged into one EFL package since 1.18 release.
# Removal in ~30 days. Bug #662510
=dev-libs/efl-1.17.0-r1
media-libs/elementary
media-plugins/emotion_generic_players
media-plugins/evas_generic_loaders
x11-themes/ethemes
Note: Upgrading to >=dev
> Your PR brokes tree:
> https://github.com/gentoo/gentoo/pull/9388#issuecomment-408914903
>
> Please fix these issues as well, for both QA and CI checks. (These
> problems may be a result of ยง1 (not yet submitted changes to the
> tree).
Thanks, done.
>
> It would be easier if your will split y
On 31/07/2018 09:35, Dirkjan Ochtman wrote:
> On Mon, Jul 30, 2018 at 5:02 PM gibix wrote:
>
> As far as I know, the Rust ecosystem is largely bimodal: stuff is either
> compatible with stable and later, or it works only on nightly. It seems
> very rare that code is actually tied to a particular
On Mon, Jul 30, 2018 at 5:02 PM gibix wrote:
> This will allows projects like rustfmt, clippy, bindgen that need runtime
> linking with the proper rust version to work correctly. Beyond this while
> rust is getting older as project we will see more projects that will
> require a specific rust ver
