I have a question regarding “www/drupal8” and configuring for multiple sites.
From what I have read, it seems that there are quite a few users who feel it
is neither safe nor advisable to do it the way the Drupal8 documentation says.
I have another solution that I thought might be serviceable.
Aft
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
Hello.
I'm working on porting Torch7, a scientific framework written in Lua:
https://reviews.freebsd.org/D12559
Torch7 has a generic install script and I'm using it to determine
dependencies need for the port. Amongst other things, Torch7 seems to
prefer LuaJIT over other lua implementations, so
On (11/08/17 20:31), John W. O'Brien wrote:
On 2017/11/07 19:16, Ryan Steinmetz wrote:
On (11/06/17 22:11), John W. O'Brien wrote:
Hello FreeBSD ports,
The maintainer of net/freeradius3 is unresponsive on two open bugs, both
with proposed patches.
John,
I was reviewing these two issues ton
Hi,
Bugzilla[1] lists three new and one open PR for mail/opendkim. Is the
port still maintained?
The port does not build with security/openssl-devel. There is a patch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828466
https://sourceforge.net/p/opendkim/patches/37/
https://git.archlinux.or
Gleb Popov <6year...@gmail.com> writes:
> Another question is how to handle lua packages that can work with different
> lua versions (like py27- and py36- ports, for instance). The example of
> such port is devel/lua-Penlight, as you can see it is basically a bunch of
> .lua files, which I decided
Hi!
> Bugzilla[1] lists three new and one open PR for mail/opendkim. Is the
> port still maintained?
Yes, but some of the PRs are difficult to parse.
> The port does not build with security/openssl-devel. There is a patch:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828466
> https://s
On Thu, 09 Nov 2017 18:42:17 +0100, Kurt Jaeger wrote:
>
> Hi!
>
> > Bugzilla[1] lists three new and one open PR for mail/opendkim. Is the
> > port still maintained?
>
> Yes, but some of the PRs are difficult to parse.
>
> > The port does not build with security/openssl-devel. There is a patch:
Hi!
> > > Can you/anyone commit it?
> >
> > A simple build-test looks OK (but fails if LUA is enabled),
> > but I can't run-test it. Can you do it ?
> >
> > With LUA I've seen some strange thing on a simple build-test
> > on a loaded box, must re-do it in poudriere.
>
> Hmm, autoreconf obviously
On Thu, 09 Nov 2017 20:16:50 +0100,
Kurt Jaeger wrote:
>
> Hi!
>
> > > > Can you/anyone commit it?
> > >
> > > A simple build-test looks OK (but fails if LUA is enabled),
> > > but I can't run-test it. Can you do it ?
> > >
> > > With LUA I've seen some strange thing on a simple build-test
> >
Am 06.11.2017 um 20:19 schrieb RW:
>
> I just noticed that the bogofilter perl and shell scripts from the contrib
> directory (see below) only get installed if bogofilter is built with the
> DOCS option.
>
>
> .for i in bfproxy.pl bogofilter-milter.pl bogo.R bogofilter-qfe.sh \
>mime.ge
On Thu, 9 Nov 2017 23:12:48 +0100
Matthias Andree wrote:
> Am 06.11.2017 um 20:19 schrieb RW:
> >
> > I just noticed that the bogofilter perl and shell scripts from the
> > contrib directory (see below) only get installed if bogofilter is
> > built with the DOCS option.
> >
> >
> > .for i in bf
On 2017/11/09 09:30, Ryan Steinmetz wrote:
> On (11/08/17 20:31), John W. O'Brien wrote:
>> On 2017/11/07 19:16, Ryan Steinmetz wrote:
>>> On (11/06/17 22:11), John W. O'Brien wrote:
Hello FreeBSD ports,
The maintainer of net/freeradius3 is unresponsive on two open bugs,
both
>>
[ devel/llvm* also have the issue in their
lld 's.]
On 2017-Nov-7, at 4:43 PM, bugzilla-noreply at freebsd.org wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223383
>
> --- Comment #7 from commit-h...@freebsd.org ---
> A commit references this bug:
>
> Author: emaste
> Date: Wed Nov
Hi Brooks,
I've just found out that our `devel/llvm40' port comes without
-DLLVM_ENABLE_RTTI=ON on the CMAKE_ARGS. This is a regression
from e.g. 3.4 times when it was enabled by default.
The problem is that RTTI support is required by some consumers,
e.g. `graphics/openshadinglanguage' and `gra
15 matches
Mail list logo