https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253179
Bug ID: 253179
Summary: ports(7) man page description of 'packages' target is
out of date
Product: Documentation
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Manual Pages
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
In attempting to build packages locally, I read the documentation, and was
confused by the following pieces of text from ports(7):
...
package Make a binary package for the port. The port will
be installed if it has not already been. The
package is a .tbz file that you can use to install
the port on other machines with pkg-add(8). If the
directory specified by PACKAGES does not exist, the
package will be put into the current directory. See
PKGREPOSITORY and PKGFILE.
...
PACKAGES Used only for the package target; the base directory
for the packages tree, normally packages/ in PORTSDIR.
If this directory exists, the package tree will be
(partially) constructed. This directory does not have
to exist; if it does not, packages will be placed into
the current directory, or you can define one of
PKGREPOSITORY Directory to put the package in.
PKGFILE The full path to the package.
...
When I attempted to build a package, I was surprised not to find it in my
current working directory (the root of the port), as I hadn't specified
PACKAGES on the command line. It turns out that it is not in the current
working directory, but in work/pkg relative to the current working directory.
This probably needs updating.
When I ran find(1) to try and find the package, I was further surprised not to
find any, having used the pattern '*.tbz' as suggested by the text "a .tbz
file". In fact, ports are now .txz files. This probably needs updating.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[email protected]"
