Received: from cogitri.dev (cogitri.dev [207.180.226.74]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id E642B781E34 for <~alpine/devel@lists.alpinelinux.org>; Tue, 26 May 2020 16:35:29 +0000 (UTC) X-Virus-Scanned: Yes Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cogitri.dev; s=mail; t=1590510923; bh=45ucf/steSQWlJXZsWcgKlo5zw9+W3oOJxg7uy9DFdg=; h=Subject:From:To:Cc:In-Reply-To:References; b=p0pNdKPP2RCTXvnpCC8prOpfGwo371JlNFe0NELBEa/uZPne5h1hXEmqVSXDc2biO wC1+SbvAjUyd6gOSejv18yZIr8ECl4TiABlQgevKxt7c5N6eDxbCYihEpmy1wB98sl MufduzPdByMbxW2RCuUY8fdPy3BJMdrbusV+O7kF2EI3Bu0tWJp9B+3jfsC/M3u5YG XOMYusNz5nDk17RMEGnJpXYRl/GuiRGsyMv8TxeEodjnUJha9tSZHsTxF6JM4mK/pZ /W7Oanuj+zA3z71gk84FJQeKRGh5uWRGvHHelvPNyx1HcJDslk8iG/adWjKyDHGwS8 7MgsmQGtFgdcw== Subject: Re: Alpine 3.12.0 release candidate 1 is out From: Rasmus Thomsen To: ecsx , Natanael Copa Cc: Alpine develmopment <~alpine/devel@lists.alpinelinux.org> Date: Tue, 26 May 2020 18:35:21 +0200 In-Reply-To: References: <20200522121940.31bd4862@ncopa-desktop.copa.dup.pw> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Hello, first off, thanks for testing the RC! :) On Tue, 2020-05-26 at 15:23 +0000, ecsx wrote: > I've been using 3.12.0-RC1 for the last days and it's working well so > far. I got just a few notes. > > - There's firefox-esr and firefox in community repo now. Are they > equally maintained? Which one is recommended? It's been clear in the > past (with firefox-esr in community and firefox in testing) that you > should choose firefox-esr for stability and better support. What now? They'll both be equally well maintained, but ff-esr will stay on the supported esr version (right now 68.x), while ff (non-esr) will always be the latest release. As such you probably want to use ff-esr if you value stability (as in no UI changes, no new features etc.) and ff if you want the latest features or speed improvements. I imagine most end users will want ff (non-esr). > - python3 doesn't provide a python binary or symlink, just a python3. > The end-of-life python2 still owns `python`. For the next RC it > should be the other way around? We tried removing the /usr/bin/python symlink from python2 in time for 3.12 but unfortunately too many things in aports still rely on /usr/bin/python being python2. Unfortunately it's now too late in the release process for such a big change - but with 3.13 /usr/bin/python being python2 should be a thing of the past. > - Are there any guides for syslinux installation on modern (UEFI) > boards? I couldn't get it to work and ended up using GRUB. I could swear we have a wiki article about this (which I can't find right now though), but I have to admit I always use rEFInd or GRUB on my machines, so maybe someone else knows more about that :) > I'll keep using this RC and let you know if any bug pops up but so > far it's good. > Congrats! > Thanks! Rasmus Thomsen