On 06/29/17 21:18, Carsten Mattner wrote:
> On Thu, Jun 29, 2017 at 5:24 PM, Zachary Crownover
> wrote:
>> That won't happen unless we have an active maintainer for it with Rust that
>> can get the project to move DragonFly from tier 3 to at least tier 2. I'd
>> like to take an active role in th
On Thu, Jun 29, 2017 at 5:24 PM, Zachary Crownover
wrote:
> That won't happen unless we have an active maintainer for it with Rust that
> can get the project to move DragonFly from tier 3 to at least tier 2. I'd
> like to take an active role in that though.
Cool, and I'd like to encourage you.
>
That won't happen unless we have an active maintainer for it with Rust that
can get the project to move DragonFly from tier 3 to at least tier 2. I'd
like to take an active role in that though.
On Jun 29, 2017 9:55 AM, "Carsten Mattner" wrote:
> On Wed, Jun 28, 2017 at 6:49 AM, Michael Neumann
On Wed, Jun 28, 2017 at 6:49 AM, Michael Neumann wrote:
> Hi,
>
> I am working on getting Rust 1.18.0 into the ports. There was an issue
> with errors happening in parallel builds triggered by cargo (Rust's
> package manager also used to build Rust itself). By disabling parallel
> builds I were ab
Hi,
I am working on getting Rust 1.18.0 into the ports. There was an issue
with errors happening in parallel builds triggered by cargo (Rust's
package manager also used to build Rust itself). By disabling parallel
builds I were able to successfully bootstrap Rust 1.18.0 from 1.17.0.
I need to pro
