PRs for manpage 'pkg_add(1)'
This is an experimental report containing PRs for manpage 'pkg_add(1)' as of Tue Dec 10 07:38:30 2013 UTC. See notes.
PRs for manpage 'pkg_add(1)':
|o||2013/05/03||bin/178323||pkg_add(1) should get shipped with PACKAGEROOT with http:// for better usability|
|o||2012/03/02||bin/165602||[request] pkg_add(1) - extend PACKAGESITE lookup to include rc.conf.local|
|o||2011/11/19||bin/162681||portmgr||pkg_add(1): new installer does not add doc packages|
|o||2011/06/25||bin/158296||portmgr||pkg_add(1) does not search entire PKG_PATH for dependencies|
|o||2010/10/03||bin/151187||pkg_add(1): allow different pkgdep location|
|o||2010/10/03||bin/151168||pkg_add(1): pkg_add -K should preserve file metadata|
|o||2010/04/16||bin/145763||portmgr||pkg_add(1) doesn't fetch packages from other architectures|
|o||2010/03/28||bin/145100||portmgr||[patch] pkg_add(1) - remove hardcoded versioning data from add/main.c|
|o||2010/02/09||bin/143698||portmgr||pkg_add(1) probably behaving incorrectly|
|o||2009/01/25||bin/130993||pkg_add(1): pkg_add -n falsely reports present local packages as missing|
|o||2008/07/24||bin/125932||portmgr||pkg_add(1) doesn't prompt for root credentials and then fails badly|
|o||2008/02/28||bin/121165||pkg_add(1) prints a weird message: PKG_TMPDIR environment variable to a location with at least 0 bytes|
|o||2007/05/14||bin/112673||portmgr||[patch] pkg_add(1): pkg_add -S leaks the temp dir|
|o||2006/03/02||bin/94032||portmgr||[patch] Enhancement to pkg_add(1) to add -4 flag to force ipv4|
|o||2006/02/06||bin/92866||portmgr||pkg_add(1) should return a different result code if package is installed|
|s||2004/02/17||bin/62965||portmgr||pkg_add(1) -r fails if fetching multiple packages at a time|
|s||2003/05/31||bin/52826||portmgr||[request] Adding Timestamps to pkg info upon pkg_add(1)|
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 linimon@FreeBSD.org. 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.