Summary: | ports-mgmt/pkg: 12.0 pkg -r error message | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Poul-Henning Kamp <phk> |
Component: | Ports Framework | Assignee: | Port Management Team <portmgr> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | ports-bugs |
Priority: | --- | Keywords: | needs-qa |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Poul-Henning Kamp
2018-12-16 18:13:38 UTC
this is not a pkg(8) bug, this is a port bugs, most of the ports are not yet friendly with pkg -r If pkg -r is not ready for prime time, maybe the manual page should have a footnote to that effect ? pkg -r is ready for prime time, the ports are not! That may be true in a very specific and narrow sense, but I don't think a lot of people will think of it that way... I have never understood the use case of pkg -r, I have always used pkg -c instead. pkg -r is a rootdir, aka no chroot, the main purpose of this option is to allow cross installation. For instance, create a armv6 image in which you do install packages, but do that from your amd64 laptop. pkg -r is quite used for such purpose today. pkg -r is also used by some people packaging stuff but not using the ports tree at all (yes pkg is not entirely tight to the ports tree). Again @sample is not a pkg thing it is a port thing (see the Keywords directory). And that @sample is not yet ready for pkg -r. meaning the ports tree is not ready. If you find a way to document that properly, I will be more that happy to improve the documentation. Time out my own ticket. |