Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pkgin conflates variables from adjacent packages #31

Open
esproul opened this issue Aug 8, 2014 · 1 comment
Open

pkgin conflates variables from adjacent packages #31

esproul opened this issue Aug 8, 2014 · 1 comment

Comments

@esproul
Copy link

esproul commented Aug 8, 2014

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
Copy link
Contributor

iMilnb commented Jan 2, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants