Re: make php to multi packages

[Takahiro Kambe <taca%NetBSD.org@localhost>]

In message <rmijz9w658j.fsf%s1.lexort.com@localhost>
	on Tue, 11 Feb 2025 07:22:20 -0500,
	Greg Troxel <gdt%lexort.com@localhost> wrote:
> It sounds like you are trying to have php detect if there is a version
> installed, and essentially treat that as if the user had defined
> PHP_VERSION_DEFAULT.
Yes.

> I see this as adding a way to work around not setting
> PHP_VERSION_DEFAULT, when really it's easy to set.   And, it is
> different from how python works.
lang/php?? packages were previously only one pacakge can be installed,
so it would help migration adding support for checking installed php.
Of course, it is transient technique.

> Additionally, it's fragile.  Suppose php82 is default, but someone wants
> php83 and installs it, and builds some packages.  Then they install a
> package that accepts only php80, so that gest installed.  The next
> package they build will use php82 because there are two.
Yes, it's fragile and only for migration stage.

If someone want to use not default version, then they should set
PHP_VERSION_DEFAULT.

> It seems much simpler to just have people set PHP_VERSION_DEFAULT if
> they don't want the pkgsrc-specified default, and it leads to very well
> understood easy to explain behavior.
After next (or one more next) branching, support for installed PHP
package function should be retired.

-- 
Takahiro Kambe <taca%NetBSD.org@localhost>