On Sun, Mar 7, 2010 at 10:26 PM, LuKreme wrote:
> On 7-Mar-2010, at 10:08, LuKreme wrote:
> On 7-Mar-2010, at 08:31, Royce Williams wrote:
>>
>>> Semi-OT, but portsnap(8) makes fetching the ports indexes no longer
>>> necessary.
>
>> I'd never heard of it, but am reading the man page now. Sounds g
On 7-Mar-2010, at 10:08, LuKreme wrote:
On 7-Mar-2010, at 08:31, Royce Williams wrote:
>
>> Semi-OT, but portsnap(8) makes fetching the ports indexes no longer
>> necessary.
> I'd never heard of it, but am reading the man page now. Sounds great!
Quick question, if I do portsnap cron in the cron
On 7-Mar-2010, at 08:31, Royce Williams wrote:
>
> On Sat, Mar 6, 2010 at 3:40 PM, LuKreme wrote:
>> On 06-Mar-10 05:07, RW wrote:
>>> portversion get its version information from the index file. You need
>>> to do a "make fetchindex" in the ports directory (or "make index" if you
>>> have a lot
On Sat, Mar 6, 2010 at 3:40 PM, LuKreme wrote:
> On 06-Mar-10 05:07, RW wrote:
>> portversion get its version information from the index file. You need
>> to do a "make fetchindex" in the ports directory (or "make index" if you
>> have a lot of time on your hands).
>
> Thanks for that, I am planni
On 06-Mar-10 05:07, RW wrote:
On Fri, 5 Mar 2010 22:29:06 -0700
LuKreme wrote:
3.3.0 was available on my machine as of 19 Feb. I have no idea what
portversion's problem is/was.
portversion get its version information from the index file. You need
to do a "make fetchindex" in the ports direct
On Fri, 5 Mar 2010 22:29:06 -0700
LuKreme wrote:
> On 5-Mar-2010, at 11:45, LuKreme wrote:
> >
> > On 04-Mar-10 21:41, James Smallacombe wrote:
> >> I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer
> >> one from FreeBSD Ports.
> >
> > Really? I just did a update of the port tre
On 5-Mar-2010, at 11:45, LuKreme wrote:
>
> On 04-Mar-10 21:41, James Smallacombe wrote:
>> I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer one
>> from FreeBSD Ports.
>
> Really? I just did a update of the port tree and yet
>
> $ portversion p5-Mail-SpamAssassin
> p5-Mail-SpamA
On 05-Mar-10 12:27, RW wrote:
On Fri, 05 Mar 2010 11:45:57 -0700
LuKreme wrote:
On 04-Mar-10 21:41, James Smallacombe wrote:
I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer
one from FreeBSD Ports.
system SA has not updated in ports to 3.3.0 yet
It's been in ports for
On 05-Mar-10 12:03, James Smallacombe wrote:
On Fri, 5 Mar 2010, LuKreme wrote:
On 04-Mar-10 21:41, James Smallacombe wrote:
I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer one
from FreeBSD Ports.
Really? I just did a update of the port tree and yet
$ portversion p5-Mail-S
On Fri, 05 Mar 2010 11:45:57 -0700
LuKreme wrote:
> On 04-Mar-10 21:41, James Smallacombe wrote:
> > I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer
> > one from FreeBSD Ports.
>
> system SA has not updated in ports to 3.3.0 yet
It's been in ports for about a month.
On Fri, 5 Mar 2010, LuKreme wrote:
On 04-Mar-10 21:41, James Smallacombe wrote:
I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer one
from FreeBSD Ports.
Really? I just did a update of the port tree and yet
$ portversion p5-Mail-SpamAssassin
p5-Mail-SpamAssassin=
$ wh
Quoting LuKreme :
On 04-Mar-10 21:41, James Smallacombe wrote:
I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer one
from FreeBSD Ports.
Really? I just did a update of the port tree and yet
$ portversion p5-Mail-SpamAssassin
p5-Mail-SpamAssassin=
$ where SpamAssassi
On 04-Mar-10 21:41, James Smallacombe wrote:
I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer one
from FreeBSD Ports.
Really? I just did a update of the port tree and yet
$ portversion p5-Mail-SpamAssassin
p5-Mail-SpamAssassin=
$ where SpamAssassin
p5-Mail-SpamAssass
A manually.
See my previous email...even after deinstalling perl 5.10 and cleaning SA
in ports, it would still list 5.10 as a dependency...I'm not entirely sure
how the SA port determines what version of perl is already installed, if
any.
and fixed the startup script,
By the sound of it
On Fri, 5 Mar 2010, Michael Scheidell wrote:
On 3/4/10 11:41 PM, James Smallacombe wrote:
I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer one from
FreeBSD Ports. It seems that at least the Ports version thinks that the
latest SA requires perl 5.10.x, rather than 5.8.9
On Fri, 5 Mar 2010 10:21:28 -0500 (EST)
James Smallacombe wrote:
> On Fri, 5 Mar 2010, RW wrote:
>
> > On Thu, 4 Mar 2010 23:41:38 -0500 (EST)
> > James Smallacombe wrote:
> >
> >> Installing from ports automatically installs perl
> >> 5.10.1 which causes spamc children to run
On 3/4/10 11:41 PM, James Smallacombe wrote:
I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer one
from FreeBSD Ports. It seems that at least the Ports version thinks
that the latest SA requires perl 5.10.x, rather than 5.8.9, which I
was already using. Installing from
On Fri, 5 Mar 2010, RW wrote:
On Thu, 4 Mar 2010 23:41:38 -0500 (EST)
James Smallacombe wrote:
Installing from ports automatically installs perl
5.10.1 which causes spamc children to run wild and basically, spamd
can't cope with it.
I don't need or want perl 5.bleeding.ed
On Thu, 4 Mar 2010 23:41:38 -0500 (EST)
James Smallacombe wrote:
> Installing from ports automatically installs perl
> 5.10.1 which causes spamc children to run wild and basically, spamd
> can't cope with it.
> I don't need or want perl 5.bleeding.edge, 5.8.9 was working just
>
I tried to upgrade from SA 3.2.5 to 3.3.0 by installing the newer one from
FreeBSD Ports. It seems that at least the Ports version thinks that the
latest SA requires perl 5.10.x, rather than 5.8.9, which I was already
using. Installing from ports automatically installs perl 5.10.1 which
Henrik Krohns writes:
> Anyone running SA on Perl 5.10 already? Any hiccups? Speedups from the new
> regex optimizations?
It should work fine; I tested with bleadperl a few months back without
problem. At that time I noted a good speedup, but when I re-tested with
the released version of
21 matches
Mail list logo
