Re: CVS commit: pkgsrc/sysutils/ansible

[Jonathan Perkin <jperkin%joyent.com@localhost>]

* On 2019-12-01 at 12:47 GMT, Adam Ciarcinski wrote:

> Module Name:  pkgsrc
> Committed By: adam
> Date:         Sun Dec  1 12:47:10 UTC 2019
> 
> Modified Files:
>       pkgsrc/sysutils/ansible: Makefile PLIST distinfo
> Removed Files:
>       pkgsrc/sysutils/ansible/patches: patch-docs_man_man1_ansible
>           patch-docs_man_man1_ansible-asciidoc
>           patch-docs_man_man1_ansible-galaxy
>           patch-docs_man_man1_ansible-galaxy-asciidoc
>           patch-docs_man_man1_ansible-playbook
>           patch-docs_man_man1_ansible-playbook-asciidoc
>           patch-examples_ansible patch-examples_hosts
>           patch-lib_ansible_callbacks patch-lib_ansible_constants
>           patch-lib_ansible_modules_core_system_ping
>           patch-lib_ansible_modules_core_system_setup
>           patch-lib_ansible_modules_extras_database_misc_riak
>           patch-lib_ansible_modules_extras_monitoring_nagios
>           patch-lib_ansible_modules_extras_packaging_os_pkgin
>           patch-plugins_README patch-plugins_inventory_cobbler
>           patch-plugins_inventory_collins
> 
> Log Message:
> ansible: updated to 2.9.1

Thanks for the update, but just be aware that by re-using
sysutils/ansible for v2 instead of continuing with sysutils/ansible2,
any binary package users who already had ansible2 installed will now
not get updates for that package, as the PKGPATH has changed.

It might be worth adding a PREV_PKGPATH entry for it, though this
isn't yet hooked up in pkgin at least.  Whilst retaining
sysutils/ansible2 may have looked a bit odd, it would have avoided
burdening users with manual upgrades, or upgrade failures when the
existing package becomes incompatible with newer dependencies.

-- 
Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com