Date: Mon, 17 May 2021 22:17:32 +0200
To: ~alpine/devel@lists.alpinelinux.org
Subject: Re: Proposal for next steps in support of riscv64 in Alpine
From: =?UTF-8?Q?S=C3=B6ren?= Tempel <soeren@soeren-tempel.net>
References: 
 <CAMmSBy-3=MYWhjSVJ1aiMy01mNZxNkERxfvFUpAs6Uwf0sdFgw@mail.gmail.com>
In-Reply-To: 
 <CAMmSBy-3=MYWhjSVJ1aiMy01mNZxNkERxfvFUpAs6Uwf0sdFgw@mail.gmail.com>
Message-Id: <2TM9JLZJSHZ31.2Q8Y9DMYGMSGV@8pit.net>
User-Agent: Mutt/1.8.3 (2017-05-23)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Roman Shaposhnik <roman@zededa.com> wrote:
> Hi!

Hi!

>      2. bundled config.sub not being recent enough to recognize riscv64.
>      The workaround I used for now is:
>                cp /usr/share/abuild/config.sub .
>       in the build() function. On top of that:
>             2.1. I can make it conditional based on riscv64
>             2.2. I can, possibly (if there's a lot desire), turn it into =
patches
>                    against bundled config.sub. This, however will increas=
e
>                    the maintenance cost and is effectively equivalent to =
the
>                    above cp statement anyway.

Just use the update_config_sub() function provided by abuild:

	https://gitlab.alpinelinux.org/alpine/abuild/-/blob/ac3ee42458ebb6204c7513=
5cbeb30201777e4116/abuild.in#L644

>       3. There's a few packages that come out with TEXTRELs and thus
>       fail the postcheck() by default. They seem to be fully functional
>       otherwise. For now, I'm proposing to disable the postcheck based
>       on riscv64 case statement. Please let me know if there's a fundamen=
tal
>       disagreement with this approach.

It's generally preferable to investigate why sanity checks fails and fix
the underlying failure reason instead of disabling a check. I think there
is currently not a single aport in aports.git which disables postchecks.

>         7. Finally, for whatever reason sha512 sums have changed for down=
loaded
>         artifacts (a good cluster is around acf-* packages). Not sure
> what's up with
>         that, but it surely doesn't seem riscv64 related (and btw, all
> of them built fine
>         when I manually updated the checksums).

Happens, these general download issues will also be fixed anyhow as we
are currently rebuilding all packages for the upcoming 3.14 release.

Greetings,
S=C3=B6ren