| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Approved by: portmgr (implicit)
Feature safe: yes
Redports: ignore
Notes:
svn path=/head/; revision=305921
|
|
|
|
|
|
|
|
| |
PR: ports/170886
Approved by: maintainer timeout (cm@therek.net, >2 weeks)
Notes:
svn path=/head/; revision=303777
|
|
|
|
|
|
|
| |
Approved by: portmgr@ (bapt@)
Notes:
svn path=/head/; revision=300239
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ports use BUILD_DEPENDS:= ${RUN_DEPENDS}. This patch fixes ports that are
currently broken. This is a temporary measure until we organically stop using
:= or someone(s) spend a lot of time changing all the ports over.
Explicit duplication > := > = and this just moves ports one step to the left
Approved by: portmgr
Notes:
svn path=/head/; revision=289563
|
|
|
|
| |
Notes:
svn path=/head/; revision=276999
|
|
|
|
|
|
|
|
| |
PR: 133029
Submitted by: Cezary Morga <cm@therek.net> (maintainer)
Notes:
svn path=/head/; revision=230971
|
|
hard to be compatible with PAR packaged applications.
The problem is, that the concept of having a distribution or module specific
share directory becomes a little hazy when you're loading everything from
a single file. PAR uses an @INC hook to intercept any attempt to load a module.
File::ShareDir uses the directory structure that is typically found in the
directories that are listed in @INC for storing the shared data. In a PAR
enviroment, this is not necessarily possible.
WARNING:
This module contains highly experimental code. If you want to load
modules from .par files using PAR and then access their shared directory
using File::ShareDir, you probably have no choice but to use it.
WWW: http://search.cpan.org/dist/File-ShareDir-PAR/
PR: ports/132406
Submitted by: Cezary Morga <cm at therek.net>
Notes:
svn path=/head/; revision=230139
|