On 22.09.2013 08:18, Victor Sudakov wrote:
> Mark Linimon wrote:
>> On Sat, Sep 21, 2013 at 10:40:09PM +0700, Victor Sudakov wrote:
>>> Could you update the port please?
>>
>> The best way to help with this is to file a PR; with the patches
>> (if you have already made them).
>>
>
> Andrey,
>
>
Mark Linimon wrote:
> On Sat, Sep 21, 2013 at 10:40:09PM +0700, Victor Sudakov wrote:
> > Could you update the port please?
>
> The best way to help with this is to file a PR; with the patches
> (if you have already made them).
>
Andrey,
Do you care to prepare the patches or should I do it?
-
Andrey V. Elsukov wrote:
> >
> > The net-mgmt/netmond port is very old. netmond-2.3.7 is already
> > available at http://people.freebsd.org/~ae/netmond-2.3.7.tgz
> >
> > Could you update the port please?
> >
> > I have tested netmond-2.3.7 on 8.4-RELEASE i386 with about 80 objects,
> > it works
On 21.09.2013 19:40, Victor Sudakov wrote:
> Dear Colleagues,
>
> The net-mgmt/netmond port is very old. netmond-2.3.7 is already
> available at http://people.freebsd.org/~ae/netmond-2.3.7.tgz
>
> Could you update the port please?
>
> I have tested netmond-2.3.7 on 8.4-RELEASE i386 with about 80
On 9/21/2013 5:47 AM, Bryan Drewery wrote:
> Ports now support enabling Stack Protector [1] support on FreeBSD 10
> i386 and amd64, and older releases on amd64 only currently.
>
> Support may be added for earlier i386 releases once all ports properly
> respect LDFLAGS.
>
> To enable, just add WIT
On Sat, Sep 21, 2013 at 10:40:09PM +0700, Victor Sudakov wrote:
> Could you update the port please?
The best way to help with this is to file a PR; with the patches
(if you have already made them).
mcl
___
freebsd-ports@freebsd.org mailing list
http://l
On 9/21/2013 5:08 PM, Big Lebowski wrote:
> Hi,
>
> Thanks for your comments, see mine below.
>
>
> On Fri, Sep 20, 2013 at 9:37 PM, Bryan Drewery wrote:
>
>> On Fri, Sep 20, 2013 at 06:57:52PM +0100, Big Lebowski wrote:
>>> Hi list!
>>>
>>> I've been working for couple last days on porting Ba
On 9/21/2013 5:08 PM, Big Lebowski wrote:
> On Fri, Sep 20, 2013 at 10:26 PM, Bryan Drewery wrote:
>
>> You also need this in the pkg-plist to fix it being a leftover:
>>
>> @dirrmtry %%RIAK_DBDIR%%
>>
>
> Unfortunately this doesnt work, because it gets expanded to
> /usr/local//var/db/riak fr
On Sat, Sep 21, 2013 at 9:48 PM, Dimitry Andric wrote:
> On Sep 21, 2013, at 21:58, Big Lebowski wrote:
> ...
> > While this is of course true, their package has some issues:
> >
> > * it doesnt work with pkgng - mine, built with make package from port
> does
> > * it is using and requiring sudo
On Fri, Sep 20, 2013 at 10:26 PM, Bryan Drewery wrote:
> You also need this in the pkg-plist to fix it being a leftover:
>
> @dirrmtry %%RIAK_DBDIR%%
>
Unfortunately this doesnt work, because it gets expanded to
/usr/local//var/db/riak from pkg-plist. That's why its not there.
B.
>
> That w
Hi,
Thanks for your comments, see mine below.
On Fri, Sep 20, 2013 at 9:37 PM, Bryan Drewery wrote:
> On Fri, Sep 20, 2013 at 06:57:52PM +0100, Big Lebowski wrote:
> > Hi list!
> >
> > I've been working for couple last days on porting Basho Riak database
> > (latest version 1.4.2) and finally
Thank you all for your work and valuable comments! Please, test the latest
version of the port, that you can find here:
https://www.dropbox.com/s/me9ej0br78ayws1/riak.20130921.tgz
and let me know if you can find any issues.
Kind regards,
B.
On Fri, Sep 20, 2013 at 6:57 PM, Big Lebowski wrote
On 9/19/13, Gary Aitken wrote:
> On 09/19/13 12:46, grarpamp wrote:
>
>> Hi. I see that a gimp port exists so I went to try the gimp package
>> but could not find it in the stable i386 package branches on
>> the FTP server, or in say 9 stable amd64. Is there a problem
>> building or distributing i
Dear Colleagues,
The net-mgmt/netmond port is very old. netmond-2.3.7 is already
available at http://people.freebsd.org/~ae/netmond-2.3.7.tgz
Could you update the port please?
I have tested netmond-2.3.7 on 8.4-RELEASE i386 with about 80 objects,
it works just fine.
--
Victor Sudakov, VAS4-RI
On 9/21/2013 9:26 AM, Nathan Whitehorn wrote:
> On 09/21/13 09:09, Bryan Drewery wrote:
>> On 9/21/2013 9:00 AM, Nathan Whitehorn wrote:
>>> On 09/21/13 05:47, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on a
On 09/21/13 09:09, Bryan Drewery wrote:
On 9/21/2013 9:00 AM, Nathan Whitehorn wrote:
On 09/21/13 05:47, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Why only those architectures?
-Nathan
On 9/21/2013 9:00 AM, Nathan Whitehorn wrote:
> On 09/21/13 05:47, Bryan Drewery wrote:
>> Ports now support enabling Stack Protector [1] support on FreeBSD 10
>> i386 and amd64, and older releases on amd64 only currently.
>>
>
> Why only those architectures?
> -Nathan
I was only able to test on
On 09/21/13 05:47, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Why only those architectures?
-Nathan
___
freebsd-ports@freebsd.org mailing list
On 09/09/2013 17:52, Niclas Zeising wrote:
>> The attached patch, also available in the latest updated version at
>> http://people.freebsd.org/~zeising/xorg-mesaupdate.diff
>> updates various xorg related libraries and drivers, most of this is
>> visible for all users of xorg.
>> xorg-server now ha
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Support may be added for earlier i386 releases once all ports properly
respect LDFLAGS.
To enable, just add WITH_SSP=yes to your make.conf and rebuild all ports.
The d
Two new port Makefile knobs are to be committed to the ports tree in a
couple of days or few weeks.
PYDISTUTILS_AUTOPLIST
This knob will enable the creation of an automatic package list similar
to the linux rpm ports and rubygems. It will work for the majority
packages that do not install files o
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
24 matches
Mail list logo