> On Feb 23, 2017, at 10:48, Craig Treleaven <ctrelea...@macports.org> wrote:
>
> Craig Treleaven (ctreleaven) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/4606c62b254f469098fe72805b99c13e81ec1839
>
> The following commit(s) were added to refs/heads/master by this push:
>
> new 4606c62 darktable: update to 2.2.3
>
> 4606c62 is described below
>
>
> commit 4606c62b254f469098fe72805b99c13e81ec1839
>
> Author: Craig Treleaven <ctrelea...@macports.org>
> AuthorDate: Thu Feb 23 11:42:25 2017 -0500
>
>
> darktable: update to 2.2.3
>
>
>
> Major reworking of darktable port. Project is now hosted on github,
> significant
>
> changes to deps (including update to gtk3), only builds with quartz.
>
>
>
> Minor functional testing so far other than to launch and display jpegs.
>
>
>
> See https://trac.macports.org/ticket/43286
>
> Believed to:
>
> Fix https://trac.macports.org/ticket/43199
>
> Fix https://trac.macports.org/ticket/47226
>
> Fix https://trac.macports.org/ticket/51447
> +github.setup darktable-org darktable 2.2.3 release-
> +# distfile is actually gzip but has xz extension?
> +distfiles ${name}-${version}.tar.xz
> +checksums rmd160 05afa3d4b7778ee1d7d2a04cf2fb87487f5650d8 \
> + sha256
> 60fb250bd78ea45f57476807bb31d141240292e03b73cb8b3417a8148cc16d7c
No.
The darktable-2.2.3.tar.xz release tarball is xz-compressed.
But you haven't instructed the portfile to download that file; you're using the
defaults of the github portgroup, which is to download the
automatically-generated gz-compressed tarball. GitHub lets you specify *any*
filename when requesting that tarball, which is why specifying an xz filename
"works" but gives you a gz file, and which is why by custom we don't specify a
filename and instead let the defaults of the github portgroup apply.
To use a release download instead, set "github.tarball_from releases". And
remove the distfiles line and set "use_xz yes". And update the checksums. And
use the stealth update recipe.
