[macports-ports] branch master updated: devel/automake: update to 1.16.1

[Ryan Schmidt]

On Mar 15, 2018, at 12:59, Adam Mercer wrote:

> Perry E. Metzger (pmetzger) pushed a commit to branch master
> in repository macports-ports.
> 
> 
> https://github.com/macports/macports-ports/commit/91908eac567b132d1696e43dc149fc7d7c994c1b
> 
> The following commit(s) were added to refs/heads/master by this push:
> 
>      new 91908ea  devel/automake: update to 1.16.1


> diff --git a/devel/automake/Portfile b/devel/automake/Portfile
> index 036a575..013fe1a 100644
> --- a/devel/automake/Portfile
> +++ b/devel/automake/Portfile
> @@ -9,7 +9,7 @@ name                automake
>  # Otherwise glibtoolize will provide an incompatible version of aclocal.m4
>  # from the older version of automake.
>  # cf: ${prefix}/share/libtool/aclocal.m4
> -version             1.15.1
> +version             1.16.1
>  
>  categories          devel
>  platforms           darwin freebsd
> @@ -30,8 +30,9 @@ depends_build       port:autoconf
>  installs_libs       no
>  
>  master_sites        gnu
> -checksums           rmd160  3dfd5d5aa037db5aae281829539eef328694cd75 \
> -                    sha256  988e32527abe052307d21c8ca000aa238b914df363a617e38f4fb89f5abf6260
> +use_xz              yes
> +checksums           rmd160  8c2a91e8fc0595dbf4854be3cef4d14bb8c5e756 \
> +                    sha256  5d05bb38a23fd3312b10aea93840feec685bdf4a41146e78882848165d3ae921

This works right now, but it's very easy for this to cause problems in the future, because it means xz and xz's dependencies can't use automake; if they did, it would be a circular dependency and new installs would fail with a confusing lack of error message.


> diff --git a/devel/libtool/Portfile b/devel/libtool/Portfile
> index bf2f7bb..6fe2b04 100644
> --- a/devel/libtool/Portfile
> +++ b/devel/libtool/Portfile
> @@ -4,7 +4,7 @@ PortSystem          1.0
>  
>  name                libtool
>  version             2.4.6
> -revision            4
> +revision            5

libtool doesn't depend on automake, so automake isn't even active on the buildbot when libtool builds, so there's no way that the libtool build could be affected by the automake upgrade there. Maybe the comment in the automake portfile that says to do this is outdated. The comment was unfortunately added without reference to a ticket or other further information.

https://github.com/macports/macports-ports/commit/3dad98162f023b36f2c4f7b4971e9ebeb118e7c5

Jeremy, do you remember any more details?