pkgin conflates variables from adjacent packages

[esproul]

Using:
pkgin 0.6.4 for SunOS-5.11 x86_64 (using SQLite 3.8.4.1) on SmartOS 14.1

I am creating my own packages, and due to a bit of carelessness when constructing the plist, ended up with my @pkgdep lines before @name, yielding something like the following in pkg_summary:

PKGNAME=my-first-pkg-1.0
...

PKGNAME=my-next-pkg-3.0
...

DEPENDS=my-first-pkg
PKGNAME=my-last-pkg-2.0
...

The first two packages are standalone-- no deps. The last package depends on my-first-pkg. What surprised me was that a pkgin install my-next-pkg caused the dependency from "my-last-pkg" to also be installed. Despite blank lines apparently being the delimiter in pkg_summary, pkgin seems to be conflating any dependencies from the trailing package with the one preceding it.

My workaround was to fix my process so that @name was always first in the plist, but given what I understand from pkg_summary(5), the order should not matter. It seems as though pkgin is using PKGNAME as the delimiter instead.

[iMilnb]

IIRC when I first wrote pkgin, there was no empty line between packages, so I relied on PKGNAME or CONFLICTS. Honestly, my life would have been easier with that blank line from the beginning :)
I'll work on this, thanks for the report.