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

Site Navigation

PRs for tag 'bsd.port.mk'

This is an experimental report containing PRs for tag 'bsd.port.mk' as of 4-20-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.


PRs for tag 'bsd.port.mk':
SSubmittedTrackerResp.Description
o2014/04/16ports/188708portmgr[bsd.port.mk] ports framework CONFLICT_INSTALL regression with staged ports
o2014/04/16ports/188693portmgr[bsd.port.mk] OPTIONS_SINGLE: bug allows user to choose two single options simultaneously
o2014/02/26ports/187084bdrewery[bsd.port.mk] only display " - found" for library once
o2013/12/11ports/184673portmgr[bsd.port.mk] abort when a dependency's ports directory doesn't exist
o2013/11/25ports/184285portmgr[bsd.port.mk][regression][patch] checking for STRIP doesn't work with OPTIONSng
o2013/10/28ports/183379portmgr[bsd.port.mk] remove "security" check from b.*.m
o2013/07/20ports/180705portmgr[bsd.port.mk] patching a file with both EXTRA_PATCHES and files/patch-* fails
o2013/06/27ports/180030bapt[bsd.port.mk] [patch] add the OPTIONS{,_}FILE rename to config-conditional.
o2013/04/23ports/178072bdrewery[PATCH] [bsd.port.mk] look for Makefile.local in ${PORTSDIR} as well as ${.CURDIR}
o2013/02/20ports/176282portmgr[bsd.port.mk] [patch] add bsd.owfs.mk
o2012/11/20ports/173731portmgr[bsd.port.mk] Doesn't clean dependency directory if not installed or call reinstall; results in build failure later
o2012/11/14ports/173620portmgr[bsd.port.mk] Recovery of the functionality of CONFLICTS among ports with different default PREFIXs, ex., between KDE4 and others
o2012/10/22ports/172964portmgr[bsd.port.mk] USE_GITHUB feature not fully implemented
o2012/10/16ports/172741bdrewery[bsd.port.mk] check-build-conflicts checks too early for pre-build targets
o2012/08/20ports/170784bdrewery[bsd.port.mk] [patch] resolve symlinks in PREFIX on deinstall
o2012/03/06ports/165781avilla[bsd.port.mk] [patch] update font ports management
o2012/02/27ports/165502portmgr[bsd.port.mk] Proposal patch for fixing TARGET_ARCH uses with somes ports
o2012/01/30ports/164638portmgr[bsd.port.mk] [patch] architecture and OS version dependent port building
o2012/01/23ports/164423portmgr[bsd.port.mk] [patch] Pass MAKE_ENV to recursive make invocations
o2012/01/23ports/164390portmgr[bsd.port.mk] make package-recursive fails with noise
f2012/01/21ports/164351portmgr[bsd.port.mk] [patch] fix simple race condition in making work directory
o2011/11/28ports/162924portmgr[bsd.port.mk] [patch] report more information at port/pkg installation
o2011/08/20ports/159946portmgr[PATCH] [bsd.port.mk] Add support for make search license=
o2011/07/15ports/158936portmgr[bsd.port.mk] Add a filename field to DESKTOP_ENTRIES
o2011/05/18ports/157168portmgr[bsd.port.mk] New hook: CONF_FILES automatically handles configuration files
o2010/12/07ports/152877portmgr[bsd.port.mk] Patch to add locking to ports make operations
f2010/07/20ports/148783portmgr[bsd.port.mk] [patch] add LATEST_LINK and CONFLICTS to INDEX
s2010/07/16ports/148695swills[bsd.port.mk] [patch] Easier / automatic regression-test target for ports
o2010/05/11ports/146496portmgr[bsd.port.mk] [PATCH] Removing ${PORTSDIR} from dependencies
s2010/03/07ports/144533portmgr[bsd.port.mk] ports tree Makefiles fail to setup a standardardized ENV
o2009/12/15ports/141641portmgr[bsd.port.mk] [patch] make 'config-recursive' finish in one pass
o2009/06/03ports/135221portmgr[bsd.port.mk] unified support for LINUX_OSRELEASE dependency
32 problems total.

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.