.pkgnew even if files didn’t previously exist

[Ben Woods]

Hi everyone,

Recently the default behaviour of pkg (or pkgbase?) was changed to install
any new files with a .pkgnew suffix.

My understand is that this was introduced to ensure pkg does not overwrite
any existing files that were not previously managed by pkg.

However, the current behaviour is that even if there was no existing file,
new files are still only being installed with the .pkgnew suffix. As the
sysadmin I then have to go looking for any .pkgnew files and remove the
suffix - this would be good to avoid overwriting existing files, but feels
over the top where no such file exists. To me, this feels like the
incorrect behaviour.

Can I please ask - is this a deliberate functionality, and if so, why?

Thanks.
Ben
-- 

--
From: Benjamin Woods
woodsb02 at gmail.com