UILD_DEPENDS= libgpg-error>=1.11:${PORTSDIR}/security/libgpg-error
> +.if defined(WITHOUT_X11) || ${OPTIONS_UNSET:MX11}
> +RUN_DEPENDS= pinentry>0:${PORTSDIR}/security/pinentry-curses
> +.else
> RUN_DEPENDS= pinentry>0:${PORTSDIR}/security/pinentry
> +.endif
>
ports. The vuXML entry:
> http://www.vuxml.org/freebsd/80771b89-f57b-11e2-bf21-b499baab0cbe.html
>
> Can we get it updated please?
>
>
--
Jun Kuriyama // FreeBSD Project
// S2 Factory, Inc.
___
freebsd-ports@freebsd.org mailing
ing the
> command gpg-agent --use-standard-socket-p which returns success if the
> standard socket option has been enabled.
I'd like to change description for STD_SOCKET option to summerize
above if someone suggests better wordings.
--
Jun Kuriyama // FreeBSD Project
// S2 Factory
[23] and 9.0 releases. But I
try building on 9-stable as of today, I finish build without problem.
I cannot any comments without error logs, sorry.
--
Jun Kuriyama // FreeBSD Project
// S2 Factory, Inc.
___
freebsd-ports@freebsd.org maili
> I've just committed a fix that solves your INDEX problem for now [1],
> but I'll still get kuriyama@ to use the new server:extract when it
> comes in.
I don't have INDEX generate testing environment for now, so can you
commit a fix?
--
Jun Kuriyama // FreeBSD Project
tional).
It seems using libpthread-stubs needs to modify configure script. Do you have a
patch for this?
--
Jun Kuriyama // FreeBSD Project
// S2 Factory, Inc.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
! pth is NOT compatible with system threads.
Can you compile security/gnupg without devel/pth installed?
--
Jun Kuriyama // FreeBSD Project
// S2 Factory, Inc.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
f you find something (bug reports, suggestions), please include Cc: to me
because I read it frequently.
--
Jun Kuriyama <[EMAIL PROTECTED]> // FreeBSD Project
<[EMAIL PROTECTED]> // S2 Factory, Inc.
___
freebsd-ports@freebsd
php5-phing port, but I received this port is
broken. The reason
is depending PEAR in post-extract stage. And installing files on
extract stage is not
our style.
I try to fix this, but I don't know this installation can work for
actual phing users. Can
someone check this patch works well?
At Fri, 30 May 2008 17:11:35 -0400,
Brian A. Seklecki wrote:
> Normally I would say that this PR may be approaching the point where we
> override the maintainer
No problem from me.
--
Jun Kuriyama <[EMAIL PROTECTED]> // S2 Factory, Inc.
<[EMAIL PROTECTED]>
> However, I have (so far) not been able to get the info files building
> properly. With the code freeze, I see no hurry to submitting
> something anyway.
Thank you for your information. I'll update after the freeze!
--
Jun Kuriyama <[E
At Fri, 25 May 2007 12:48:36 +0800,
Ganbold wrote:
> Since ports tree is unfrozen, could you integrate my patch to ports tree?
>
> Here is the patch.
> Please let me know if there is something wrong with this patch.
Thanks, committed!
--
Jun Kuriyama <[EMAIL PROTECTED]>
integrate your patch into our ports tree.
--
Jun Kuriyama <[EMAIL PROTECTED]> // S2 Factory, Inc.
<[EMAIL PROTECTED]> // IMG SRC, Inc.
<[EMAIL PROTECTED]> // FreeBSD Project
___
freebsd-po
> - PARAM_DUMP_ESTIMATE,
> + PARAM_HONOR_NODUMP,
>"s", "f", NULL);
>
> # ifdef HAVE_DUMP_ESTIMATE
Thank you for your investigation. I've committed y
pg ports will need logic to handle what to do with the symlink
> if the other port is installed.
Seems fine. Like this?
--
Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc.
<[EMAIL PROTECTED]> // FreeBSD Project
gnupg.diff
Description: Binary data
___
ld be appreciative of Jun's
> efforts, and I hope that he understands that nothing I've said is
> intended in any way to be critical of him or his work.
I appreciate Doug's work of course. This thread is just which option
we choose from possible ways. And mainly caus
e (without version number).
Using version number in ports directory is very exceptional event for
keeping old ports (like "emacs", "emacs19", "emacs20"). I thought
this is the way to indicate "what you should choose&q
At Fri, 03 Nov 2006 23:18:11 -0500,
Brian A. Seklecki wrote:
> FYI to SNMP hackers. Objections to this patch?
No problem from me. I'm preparing for 5.3.1 upgrade in my local.
This will bump shlib version, so I'll do it after 6.2R with your
patch.
--
Jun Kuriyama <[EMAIL PR
18 matches
Mail list logo
