Re: Asterisk package naming

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

D'Arcy Cain <darcy%NetBSD.org@localhost> writes:

> On 2018-08-02 01:58 PM, Greg Troxel wrote:
>> So somehow, you need to have a file that (more or less) has one line
>> describing every package you want installed, per machine, and then to
>> cat/sort/uniq these to run your bulk build.  Apparently that file right
>> now has PKGNAME in it, and your bulk build script tries to convert those
>> to PKGPATH..  That is basically troublesome, and we are suggesting that
>> instead you have control files that have PKGPATH instead.
>
> Yes, I suggested that possibility too earlier but it still works for
> everything except asterisk.  If I put comms/asterisk13 into the file
> then what pkg_info command do I give to see if it is installed?
>
> # pkg_info -Q PKGPATH comms/asterisk13
> pkg_info: can't find package `comms/asterisk13'
>
> If I split on the '/'...
>
> # pkg_info -Q PKGPATH asterisk13
> pkg_info: can't find package `asterisk13'

pkg_info -Q PKGPATH -a | egrep "^${PKGPATH}\$"

should work, modulo my getting quoting wrong.