Received: from mx1.mailbun.net (mx1.mailbun.net [170.39.20.100]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id B7044782B1E for <~alpine/devel@lists.alpinelinux.org>; Mon, 28 Jun 2021 14:36:40 +0000 (UTC) Received: from penelo.lan (unknown [107.125.25.239]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: ariadne@dereferenced.org) by mx1.mailbun.net (Postfix) with ESMTPSA id 20C491126B2; Mon, 28 Jun 2021 14:36:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dereferenced.org; s=mailbun; t=1624890998; bh=PohZF+K02uUvxehhAZGC7VucZM2cyA4jAchmuQoyecg=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Ub1RQ1x9VXwutLxPn8YxfPn/9JYza8wlk7F/PdQLtxXgyhLAg+dE3v62NtH+6TbkF 51PM7RN3Iv+VdOqdU4xU6oQWBFWOM1hlua7uDxQPKKMs11wwGNRCRzTONf7dFUbhV3 voMNTwmx6IwZFGQwsCrwl0IVvfiF4Atv6TPCVGmF4+5e2BXplii5aJCMJvV18m8FN3 Bixg9WPAGp27rjlvl1gd+VR4dPp0avj2MhLi1tXdjsDBSKrsk/onJioXQxRt2Ku5Ef MEPrvUL1KIgZoLWt9JQuZPiU8VOcQuTE2N/GsT68q6T8/GhtxLHjc9T30YjUgaFLXZ 0YX9Z31yoXXrA== Date: Mon, 28 Jun 2021 09:36:37 -0500 (CDT) From: Ariadne Conill To: Roman Shaposhnik cc: ~alpine/devel@lists.alpinelinux.org Subject: Re: Plan for RISCV64 in Alpine 3.15 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Hi, On Sun, 27 Jun 2021, Roman Shaposhnik wrote: > Hi! > > so first of all -- thank you all for taking RISCV forward > while I was traveling -- much appreciated! I see that > we now have a builder that produces packages and they > are actually getting deposited at the usual places. E.g.: > https://dl-cdn.alpinelinux.org/alpine/edge/main/riscv64/ > > Given that, here's my first few infrastructure related questions: > 1. what does it take for edge packages to show up on: > https://pkgs.alpinelinux.org/packages ? > 2. in general, do we produce the final consumable aritfacts > for the Edge builds? Things like: > https://alpinelinux.org/downloads/ > > With that out of the way, personally, I'm going to spend this > coming week making sure that: > * bootstrap.sh is back to functional > * we get to produce at least the following artifacts: > * MINI ROOT FILESYSTEM > * VIRTUAL > * see if we can get rid of !tests on builders and selectively > disable tests in those packages that just need it. The problem is that building with tests enabled under qemu is really slow. It would be nice if we can find some actually decent (at least 16 cores) builder for riscv64. The chip made by Alibaba looks promising. I wonder if we can source a board with it, somehow? > Now, the last question I have is this: what would be the criteria > for the # of packages or anything else to officially release RISCV64 > as part of Alpine 3.15? I'm not comfortable having riscv64 as a release architecture until we are building on real silicon, but if the qemu stuff proves to be otherwise solid, then I guess that's fine too if we have real QA happening on real boards. Ariadne