Asterisk package naming

[D'Arcy Cain <darcy%NetBSD.org@localhost>]

I have some automated methods for checking on installed packages that
mostly works fine but has a few small glitches.  Some, such as
apXX-phpYY (e.g. ap24-php56) are fine once I manually install them.
Asterisk, on the gripping hand, is a constant thorn.  I run Asterisk 13
but it installs as asterisk.  If I test for asterisk13 it says that it
is not installed yet.  I can't use asterisk because that's a different
package.

It was recently suggested that the asterisk package, which is an ancient
version, be removed.  I would like to suggest that we instead make
asterisk a master package that checks mk.conf for the desired version
and depends on that package.  We can default to something reasonable
such as the latest LTS version but those of us using it in production
can specify the version we want.  The other packages would need to be
changed to include the version in the name so, for example, when I
install asterisk I actually get asterisk and asterisk13.  I could either
put asterisk in my list and use mk.conf to select my version or I could
put asterisk13 in my list.  Either way, once it is installed, the
package in my list shows as installed and I won't keep building and
trying to install the same package.

Having a master package has prior art already such as Python, Apache,
PostgreSQL, etc.

Suggestions?  Comments?

-- 
D'Arcy J.M. Cain <darcy%NetBSD.org@localhost>
http://www.NetBSD.org/ IM:darcy%Vex.Net@localhost