Monday Pick (fwd)

When is the cocksucker who runs this this list going to implement some simple anti-spam provisions? Or are you one of those idiotic "frea speach" spam supporters, so prevalent amongst Americans these days? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."

Re: [PATCH] lang/python27 -- Fix namespace collision

Any chance that the patch will be added to lang/python27? -- steve On Sun, Jun 18, 2017 at 11:31:12AM -0700, Steve Kargl wrote: > On Sun, Jun 18, 2017 at 11:29:05AM -0700, Steve Kargl wrote: > > Both IEEE-754 2008 and ISO/IEC TS 18661-4 define the half-cycle > > trignometric functions cospi,

Re: Configuring options/knobs without `make config`

On 1 August 2017 at 08:16, Morse, Richard E.,MGH wrote: > On Jul 31, 2017, at 4:06 PM, Jonathan Chen wrote: >> >> Here's a quick run down on the change: >> https://forums.freebsd.org/threads/52871/ >> >> The portconf features have been baked into the

Re: Configuring options/knobs without `make config`

On Jul 31, 2017, at 4:06 PM, Jonathan Chen wrote: > > Here's a quick run down on the change: > https://forums.freebsd.org/threads/52871/ > > The portconf features have been baked into the ports system, and you > can set/unset options within /etc/make.conf, eg: > >

Re: Configuring options/knobs without `make config`

On 1 August 2017 at 07:50, Morse, Richard E.,MGH wrote: > Hi! I used to use portconf on the machine this is going to be replacing, but > it seemed like there were changes to the way the port system worked between > 8.4 and 11, and I couldn’t find anything that

Re: Configuring options/knobs without `make config`

Hi! I used to use portconf on the machine this is going to be replacing, but it seemed like there were changes to the way the port system worked between 8.4 and 11, and I couldn’t find anything that documented how to properly set up portconf for the new “options” stuff, in place of the old

FreeBSD Port: bitcoin-daemon-0.12.1_11

Hi Bartek. The Bitcoin-related ports are getting old. The upstream current released version is [0.14.2](https://github.com/bitcoin/bitcoin/releases) and the FreeBSD ports collection has 0.12.1 from November 2016. I don't know of any security issues, but a number of important new features which

Monday Pick

The most common question or request we get in our email mailbox is " How can i get the ticker before anybody else ?" , Before the rest of the stock alert subscribers ! I always give you a ticker before the rest of the world knows about it , but you guys still wait to jump on it. Isn't

Re: GNU Makefile to FreeBSD Makefile

Hi Kurt Thanks for that hint, I am trying to port the project to FreeBSD. Let's see if I can get it properly ported. Best On Mon, Jul 31, 2017 at 6:25 PM, Kurt Jaeger wrote: > Hi! > > > I am trying to port some software to FreeBSD it uses GNU Makefile > > convention that uses

Re: GNU Makefile to FreeBSD Makefile

Hi! > I am trying to port some software to FreeBSD it uses GNU Makefile > convention that uses these variables all over the place. If you are porting to FreeBSD as a port, use USES= gmake and the build process will use GNU make, so you do not need to adapt all that stuff. -- p...@opsec.eu

GNU Makefile to FreeBSD Makefile

Hey guys I am trying to port some software to FreeBSD it uses GNU Makefile convention that uses these variables all over the place. https://stackoverflow.com/questions/3220277/what-do-the-makefile-symbols-and-mean I understand what they mean all: library.cpp main.cpp - $@ evaluates to all

Re: libidn2 drags in ruby and friends

I'm waiting for approval by sunpoet (maintainer). On 29.07.2017 04:29, Randy Bush wrote: repo head is 446595, which does not have this patch. i plead for someone to commit? pretty please? :) thanks randy Attached an updated patch. I will also send it to sunpoet (maintainer) and will ask