Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'pkg_add(1)'

This is an experimental report containing PRs for manpage 'pkg_add(1)' as of Wed Apr 23 07:38:39 2014 UTC. See notes.

PRs for manpage 'pkg_add(1)':
o2013/05/03bin/178323pkg_add(1) should get shipped with PACKAGEROOT with http:// for better usability
o2012/03/02bin/165602[request] pkg_add(1) - extend PACKAGESITE lookup to include rc.conf.local
o2011/11/19bin/162681portmgrpkg_add(1): new installer does not add doc packages
o2011/06/25bin/158296portmgrpkg_add(1) does not search entire PKG_PATH for dependencies
o2010/10/03bin/151187pkg_add(1): allow different pkgdep location
o2010/10/03bin/151168pkg_add(1): pkg_add -K should preserve file metadata
o2010/04/16bin/145763portmgrpkg_add(1) doesn't fetch packages from other architectures
o2010/03/28bin/145100portmgr[patch] pkg_add(1) - remove hardcoded versioning data from add/main.c
o2010/02/09bin/143698portmgrpkg_add(1) probably behaving incorrectly
o2009/01/25bin/130993pkg_add(1): pkg_add -n falsely reports present local packages as missing
o2008/07/24bin/125932portmgrpkg_add(1) doesn't prompt for root credentials and then fails badly
o2008/02/28bin/121165pkg_add(1) prints a weird message: PKG_TMPDIR environment variable to a location with at least 0 bytes
o2007/05/14bin/112673portmgr[patch] pkg_add(1): pkg_add -S leaks the temp dir
o2006/03/02bin/94032portmgr[patch] Enhancement to pkg_add(1) to add -4 flag to force ipv4
o2006/02/06bin/92866portmgrpkg_add(1) should return a different result code if package is installed
s2004/02/17bin/62965portmgrpkg_add(1) -r fails if fetching multiple packages at a time
s2003/05/31bin/52826portmgr[request] Adding Timestamps to pkg info upon pkg_add(1)
17 problems total.


GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.

Please give feedback on this report to Thanks.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.