On 2018/02/28 18:03, Remi Pointel wrote:
Most of them look ok, but for plaso:
> -SHA256 (plaso-20180127.tar.gz) = i7wASIbQIw3HtlYU9DatjwI3/DYyx5S/zDGVzsgx1L8=
> -SIZE (plaso-20180127.tar.gz) = 110251128
> +SHA256 (plaso-20180127.tar.gz) = kA10e1j2UrkTxhSf3YnSGTPf++3KaktvT5W2OE+C8nU=
> +SIZE (plaso-20180127.tar.gz) = 109492062
----- Forwarded message from Stuart Henderson <stu@spacehopper.org> -----
From: Stuart Henderson <stu@spacehopper.org>
Date: Tue, 27 Feb 2018 22:36:51 +0000
To: Thomas Frohwein <frohwein@ymail.com>
Cc: ports@openbsd.org
User-Agent: Mutt/1.9.3 (2018-01-21)
Subject: Re: fs2open - switch to release
Mail-Followup-To: Thomas Frohwein <frohwein@ymail.com>, ports@openbsd.org
On 2018/02/27 10:16, Thomas Frohwein wrote:
> This diff switches fs2open to the release tarball. Simplifies things a ton
> because now it doesn't need to fetch the git submodules separately. Includes
> REVISION bump and new HOMEPAGE line.
>
> Builds and runs as before on a quick test run.
This is a big improvement imho. Only problem is that the distfile name
is unchanged which isn't handled very well in bulk builds at the moment
(distfiles are shared between multiple arches, which are building from
different versions of the tree - we could easily have 2 or 3 fast-arch
builds, then a slow arch tries to build it and wants the old version,
then fast arches build again, then another slow one, etc).
Obviously this is not just going to affect fs2open but some other ports
which are moved to /releases too, so let's pick a standard method to
handle it before proceeding.
> +DISTFILES = ${DISTNAME}${EXTRACT_SUFX}
This line is the default so could normally be removed. But due to the
distfile issue above I would propose this instead for now, and remove at
next update:
DISTFILES = ${DISTNAME}_1{${DISTNAME}}${EXTRACT_SUFX}
And with this the distinfo would change to:
SHA256 (fs2_open_3_8_0-source-Unix_1.tar.gz) = 0m/4tma9rh6fQquvL0mNs2EJPyKJ2nhVXx9vu6dWIic=
SIZE (fs2_open_3_8_0-source-Unix_1.tar.gz) = 9040907
Does that make sense?
----- End forwarded message -----
No comments:
Post a Comment