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
> 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
Hi!
On Mon, 30 Jul 2018 17:00:20 +0200 gibix wrote:
> Hello,
>
> I opened a PR here: https://github.com/gentoo/gentoo/pull/9388
>
> Here a copy of the message:
>
> # add support for rust multi-target
>
> - add rust.eclass (with rust-utils.class) to support rust multi-target with
> multibuild
Hello,
I opened a PR here: https://github.com/gentoo/gentoo/pull/9388
Here a copy of the message:
# add support for rust multi-target
- add rust.eclass (with rust-utils.class) to support rust multi-target with
multibuild
- modify cargo.class to support rust multi-target
- change dev-lang/rust
