Home :: Documentation :: Download :: Development :: Community :: Wiki :: Ports :: Bugs :: Links :: About
Welcome to CRUX bug tracking.
Tasklist

FS#407 - prt-get fails to find package when exporting a PKGMK_PACKAGE_DIR in pkgmk.conf

Attached to Project: CRUX
Opened by Johannes Winkelmann (jw) - Tuesday, 30 December 2008, 16:42 GMT+2
Task Type Bug Report
Category tools → prt-get
Status New
Assigned To Johannes Winkelmann (jw)
Operating System CRUX
Severity Low
Priority Normal
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

It appears that adding 'export PKGMK_PACKAGE_DIR="/usr/ports/pkg"' is not understood orrectly by prt-get; removing the 'export' fixes this
This task depends upon

Comment by Jose V Beneyto (sepen) - Tuesday, 30 December 2008, 18:45 GMT+2
iirc, prt-get search within the ports, so I suppose that you aren't talking about 'prt-get search' and maybe you mean about prt-get internals.
could you paste a better example about how prt-get fails to find a package?
Comment by Andrew Brouwers (thrice) - Sunday, 10 May 2009, 00:28 GMT+2
I've hit this too.

It occurs when another directory is used for "PKGMK_PACKAGE_DIR." An example, if I have package#1.0.pkg.tar.gz sitting in my package directory (/usr/ports/packages/), but run "prt-get install package" , pkgmk will un-necessary compile the package. However, if the package exists in the default "/usr/ports/opt/package/package#1.0.pkg.tar.gz, prt-get will simply install the package.
Comment by Jose V Beneyto (sepen) - Monday, 11 May 2009, 16:17 GMT+2
I think I found something interesting in prt-get's sourcecode (installtransaction.cpp)

[...]
630 if (StringHelper::startsWith(s, "PKGMK_PACKAGE_DIR=")) {
631 candidate = s;
632 }
[...]

The 'getPkgDestFromFile' function gets the PKGMK_PACKAGE_DIR value only when the line from pkgmk.conf starts with that word, so that could be the reason for what removing the 'export' fixes it.
Comment by Johannes Winkelmann (jw) - Monday, 11 May 2009, 16:22 GMT+2
yeah, this is must likely the reason for this. Thanks!

Loading...