Re: upgrade glitches with php, maybe

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

I just had another thought, which is that this discussion is framed in
terms of "something changed in pkgsrc and 'pkgin ug' does not handle it
seamlessly, so that's not ok".

pkgin is not part of core pkgsrc.  The sources come from an upstream,
stored on github, and change control in pkgin is not overseen by
pmc/TNF.  (I'm not claiming in the slightest that there are bad changes
or that there is anything wrong with how pkgin is maintained; I'm
pointing out the structural situation.)

pkgin is one of 2 package managers developed for pkgsrc, and today is
the one that is still maintained and works the best.  It's only
relatively recently in the history of pkgsrc that there is an
expectation that "pkgin ug" can typically operate without manual fixups.

There has never been an expectation that pkg_add/pkgin can deal with
upstream config changes.  There has never been an expectation that
pkg_add/pkgin seamlessly handles package renaming.  Yes, we try to avoid
renaming unless it's really necessary, and I have consistently ranted
against unnecessary renaming, where "unnecessary" is a trouble/benefit
tradeoff.

The PHP multiversion change was proposed, discussed, available for
testing for along period, and then went in.  It's not a driveby cowboy
update the day before the freeze.  (Again, not saying that should 100%
determine anything, but I think it's important to look at the context.)