From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:54097) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8ymO-0002av-1e for guix-patches@gnu.org; Tue, 26 Mar 2019 22:59:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h8ymM-0004Fc-Vz for guix-patches@gnu.org; Tue, 26 Mar 2019 22:59:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:47213) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h8ymM-0004FY-A7 for guix-patches@gnu.org; Tue, 26 Mar 2019 22:59:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h8ymM-0000h5-4W for guix-patches@gnu.org; Tue, 26 Mar 2019 22:59:02 -0400 Subject: [bug#34820] [PATCH] gnu: rust: Update to 1.32.0 Resent-Message-ID: References: <9E833478-6D25-4549-B90A-8244CCED81DD@gmail.com> <9FA7C98C-EFF0-4A04-A628-AB4B907D438E@gmail.com> <20190319024719.7226c75f@scratchpost.org> <20190326142148.622a46ae@scratchpost.org> <1D8916FD-CC21-4AD0-9098-78339590F353@gmail.com> <20190326191427.12846e89@scratchpost.org> <50A5BA1C-E3B1-4875-BF0E-1B09D073A94E@gmail.com> <87h8bp6q5r.fsf@posteo.net> <91DE286A-2D30-4624-B8EF-3C7B973C1A47@gmail.com> From: Brett Gilio In-reply-to: <91DE286A-2D30-4624-B8EF-3C7B973C1A47@gmail.com> Date: Tue, 26 Mar 2019 21:58:07 -0500 Message-ID: <87bm1x6n28.fsf@posteo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ivan Petkov Cc: 34820@debbugs.gnu.org Ivan Petkov writes: > Hi Brett! > >> On Mar 26, 2019, at 6:51 PM, Brett Gilio wrote: >>=20 >> LGTM, I want to try maintaining a local build for nightly which requires >> 1.33 atm. Do we have an ETA on how long until we can get that? What can >> I do to help? > > I actually have a patch ready for packaging 1.33, just been holding off to > avoid the noise while we get 1.31/1.32 built. Happy to post put it up if > you'd like to see a copy! > > As far as maintaining nightlies goes, I think it would be a challenge to > keep up manually, unless you happen to have some cron job that builds a > new version daily. I've been considering packaging rustup within guix > after 1.33 lands, which might make it possible to develop with nightly > rust without having to maintain a nightly build within guix itself. > > Not sure what challenges there may be with the rustup approach though > (will the prebuild binaries work well with guix?). I'd be happy to hear > if you make any progress though! > > =E2=80=94Ivan You are probably right, there are definitely going to be some liability issues about working with the nightly branch. But it was something I was interested in investigating. The more we deal with rust on Guix, the more I think that rustup is going to have to become a necessity if we want to attract more Rust developers to using Guix. Nightly is almost a requirement for a good few. You might be knowing that Nix has the rustup toolchain, and it seems to work fine. Although, there is the nasty linker issue which requires building all rust projects in a nix-shell with the mozilla rust channel. So, there is definitely some potential challenges there, but it is definitely something we need to investigate imo. Also, yes, please send me the patch off list. Brett