Message-ID: <72a881ad47bc7e8d79e8c7d94a9d23319fd5288f.camel@cogitri.dev>
Subject: Re: Planning for 3.12 feature freeze
From: Rasmus Thomsen <oss@cogitri.dev>
To: ~alpine/devel@lists.alpinelinux.org
Date: Mon, 30 Mar 2020 12:35:58 +0200
In-Reply-To: <20200330121403.71f8e7f9@ncopa-desktop.copa.dup.pw>
References: <20200330121403.71f8e7f9@ncopa-desktop.copa.dup.pw>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

Hello,

I don't think it's a good idea to freeze Rust completely for stable
releases. Rust upstream currently doesn't provide patch releases and
packages using Rust are usually quick to jump onto new rustc features.
As such I'd vote for keeping Rust up-to-date in stable releases. Since
it's in community (so 6 months of support) and Rust releases every 6
weeks this would mean 4~5 upgrades. I don't expect breakage from that
since Rust has a fairly sane deprecation scheme. This would also allow
us to keep firefox in community since that usually needs a recent Rust
compiler.

As for fixing the rust triplets: I started to doubt if that's actually
useful. I mean it _is_ nice to have a custom triplet with our name on
it for the options we set, but right now there are some really weird
issues during compilation with custom triplets that I can't seem to get
behind and we currently have to work around some rust crates not
working with custom triplets and needing patches (see e.g. FF).

Regards,

Rasmus

On Mon, 2020-03-30 at 12:14 +0200, Natanael Copa wrote:
> Hi!
> ...
> Once we have the builder up, we should avoid do significant changes
> in
> toolchains and dependencies that influences how packages are built.
> For example:
> 
> ...
>  - rust
> ...
> 
> I would also like to fix rust triples to be consistent[3].
> 
> 
> [1]: https://gitlab.alpinelinux.org/alpine/aports/issues/11017
> [2]: https://gitlab.alpinelinux.org/alpine/aports/issues/11260
> [3]: https://gitlab.alpinelinux.org/alpine/aports/issues/11349