Re: upgrade glitches with php, maybe

[Greg Troxel <gdt%lexort.com@localhost>]

Taylor R Campbell <riastradh%NetBSD.org@localhost> writes:

>>                           There has never been an expectation that
>> pkg_add/pkgin seamlessly handles package renaming.
>
> We have had SUPERSEDES since 2009 to handle this.
>
> If there's no expectation that the binary package tools can handle it,
> that's because we have set expectations so low they're practically six
> feet under.

I do not believe that SUPERSEDES has ever done config file migration.  I
don't remember if that got set for dovecot 1 to 2, for example (or even
if 1 is gone), but I am pretty sure it requires sysadmin thinking.  At
least it did when I migrated, and I wasn't upset by that as a pkgsrc
deficiency.

I agree that here it should be possible to migrate config files for
php-8.2.x to php82-8.2.x, as they are the same config files, just with a
change of pathname.

> But all the proposal, discussion, and availability _in the development
> tree_ appears to have missed critical details for _users_ who don't
> track tech-pkg@ and pkgsrc-changes@ -- and who do just follow the
> instructions in documentation to pkg_add or pkgin install binary
> packages.

That's fair, and I have not meant to say "this shouldn't be
fixed/changed".  Just that I disagree that we have such strong
established norms for avoiding users have to pay attention to config
files even during structural changes and renaming.