Re: Help Wanted - Work with MSFT and help finish the port of .NET Core to FreeBSD

+1 I threw some comments on the open issues. On Wed, Sep 27, 2017 at 6:36 PM, Geoffrey Huntley wrote: > Tomas and Karel from MSFT have some updates for us, in short, the full-scale > battle can start and volunteers are needed. > > - FreeBSD: implement

Re: compler warnings in ports not supported in gcc 4.2.1 (stable/10)

On 24/9/17 5:58 am, Dimitry Andric wrote: On 23 Sep 2017, at 23:42, Julian Elischer wrote: Trying to compile the emulators/open-vm-tools-nox11 port but I end up dying with: libtool: compile: cc -DPACKAGE_NAME=\"open-vm-tools\" -DPACKAGE_TARNAME=\"open-vm-tools\"

Re: Codeblocks no longer compiles on -current

Michael Butler writes: > --- sqvm.lo --- > In file included from sqvm.cpp:5: > In file included from /usr/include/c++/v1/math.h:310: > /usr/include/c++/v1/limits:148:85: error: expected expression > _LIBCPP_INLINE_VISIBILITY static _LIBCPP_CONSTEXPR type min() >

Codeblocks no longer compiles on -current

Errors all seem to be similar, of the form .. -- sqbaselib.lo --- depbase=`echo sqbaselib.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`; /bin/sh ../../../../libtool --tag=CXX--mode=compile c++ -DHAVE_CONFIG_H -I. -I../../../../src/include -I../../../../src/include/scripting/include

Re: Help Wanted - Work with MSFT and help finish the port of .NET Core to FreeBSD

Tomas and Karel from MSFT have some updates for us, in short, the full-scale battle can start and volunteers are needed. - FreeBSD: implement System.Diagnostic.Process: https://github.com/dotnet/corefx/issues/24292 - FreeBSD: System.Console is not working right:

Re: [HEADUP] FLAVORS landing.

On 27 Sep, Julian Elischer wrote: > On 27/9/17 4:20 pm, Matthew Seaman wrote: > > Before this gets too far down the road I would like to suggest that we > quickly formalise some nomenclature > or we will have 200 different ideas as to how to do the same thing; > > I would like to propose the

Re: [HEADUP] FLAVORS landing.

On Wed, 27 Sep 2017 21:24:22 +0800 Julian Elischer wrote > On 27/9/17 8:17 pm, Stefan Esser wrote: > > Am 27.09.17 um 13:52 schrieb Julian Elischer: > >> On 27/9/17 4:20 pm, Matthew Seaman wrote: > >> > >> Before this gets too far down the road I would like to suggest that we

Re: [HEADUP] FLAVORS landing.

Quoting Stefan Esser (from Wed, 27 Sep 2017 14:35:24 +0200): Am 26.09.17 um 16:05 schrieb Mathieu Arnold: Hi, **Do not commit FLAVORS to any ports, a hook will prevent it, that being said, do try it and test what can be done.** To test this feature in poudriere, you need

Re: Portmaster error

On Wed, Sep 27, 2017 at 10:22 AM, Paul Schmehl wrote: > I'm running a 10.3-RELEASE instance. I ran portmaster -ad in screen > yesterday to get all the ports up to date. Today I ran it again, to make > sure everything was updated. > > When I did, I got this error: > >

Re: Portmaster error

On 27-9-2017 17:22, Paul Schmehl wrote: > I'm running a 10.3-RELEASE instance. I ran portmaster -ad in screen yesterday > to get all the ports up to date. Today I ran it again, to make sure > everything was updated. > > When I did, I got this error: > > portmaster -ad > > ===>>> Gathering

Re: [HEADUP] FLAVORS landing.

Le 27/09/2017 à 15:24, Julian Elischer a écrit : > On 27/9/17 8:17 pm, Stefan Esser wrote: >> Am 27.09.17 um 13:52 schrieb Julian Elischer: >>> On 27/9/17 4:20 pm, Matthew Seaman wrote: >>> >>> Before this gets too far down the road I would like to suggest that we >>> quickly formalise some

Re: [HEADUP] FLAVORS landing.

On 09/27/2017 15:24, Julian Elischer wrote: > On 27/9/17 8:17 pm, Stefan Esser wrote: >> Am 27.09.17 um 13:52 schrieb Julian Elischer: >>> On 27/9/17 4:20 pm, Matthew Seaman wrote: >>> >>> Before this gets too far down the road I would like to suggest that we >>> quickly formalise some

Re: [HEADUP] FLAVORS landing.

On 27/9/17 8:17 pm, Stefan Esser wrote: Am 27.09.17 um 13:52 schrieb Julian Elischer: On 27/9/17 4:20 pm, Matthew Seaman wrote: Before this gets too far down the road I would like to suggest that we quickly formalise some nomenclature or we will have 200 different ideas as to how to do the

Re: [HEADUP] FLAVORS landing.

Am 26.09.17 um 16:05 schrieb Mathieu Arnold: > Hi, > > **Do not commit FLAVORS to any ports, a hook will prevent it, that being > said, do try it and test what can be done.** > > To test this feature in poudriere, you need > poudriere-devel-3.1.99.20170621 or later. > > This has been a long

Re: [HEADUP] FLAVORS landing.

Am 27.09.17 um 13:52 schrieb Julian Elischer: > On 27/9/17 4:20 pm, Matthew Seaman wrote: > > Before this gets too far down the road I would like to suggest that we > quickly formalise some nomenclature > or we will have 200 different ideas as to how to do the same thing; > > I would like to

Re: gettng the port revision number associated with the pkg repo.

On 26/9/17 10:07 pm, Lowell Gilbert wrote: Julian Elischer writes: SO imagine that I needed to be ab;e to reproduce the pkg repo as of a articular day, is there anywhere one can look to see the svn revision number that corresponds to teh current pkg files. I would like

Re: [HEADUP] FLAVORS landing.

On 09/27/2017 10:20, Matthew Seaman wrote: Currently the idea is to work on the python ports in the tree so we'd have both python-2.7 and python-3.6 versions built and available in the repos. That's just the initial target to debug and bed-in the FLAVORS stuff. Same applies for php56 vs

Re: [HEADUP] FLAVORS landing.

On 27/9/17 4:48 pm, Kirill Ponomarev via freebsd-ports wrote: On 09/27, Tilman Keskinöz wrote: On 2017-09-27 08:29, Matthew Seaman wrote: On 27/09/2017 07:11, Julian Elischer wrote: Is there a document/paper on what this is and what it's limits are etc?

Re: [HEADUP] FLAVORS landing.

On 27/9/17 4:20 pm, Matthew Seaman wrote: Before this gets too far down the road I would like to suggest that we quickly formalise some nomenclature or we will have 200 different ideas as to how to do the same thing; I would like to propose the following possible "examples of official"

FreeBSD ports you maintain which are out of date

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,

Re: [HEADUP] FLAVORS landing.

On 09/27, Tilman Keskinöz wrote: > > > On 2017-09-27 08:29, Matthew Seaman wrote: > > On 27/09/2017 07:11, Julian Elischer wrote: > >> Is there a document/paper on what this is and what it's limits are etc? > > > > https://wiki.freebsd.org/Ports/FlavorsAndSubPackages > >

Re: [HEADUP] FLAVORS landing.

On 27/09/2017 08:09, Tilman Keskinöz wrote: > > > On 2017-09-27 08:29, Matthew Seaman wrote: >> On 27/09/2017 07:11, Julian Elischer wrote: >>> Is there a document/paper on what this is and what it's limits are etc? >> >> https://wiki.freebsd.org/Ports/FlavorsAndSubPackages >>

Re: Porters Handbook section 4.4

Am 26.09.17 um 08:21 schrieb Kubilay Kocak: > In section: > > 4.4. Patching > > - Add new section (at/numbered 4.4.2) > - Name: Automatic Patch Generation > - Renumber sections (4.4.2 -> 4.4.3) > > Text: > > The ports framework provides a {{{makepatch}} target, which when run, >

Re: [HEADUP] FLAVORS landing.

On 2017-09-27 08:29, Matthew Seaman wrote: > On 27/09/2017 07:11, Julian Elischer wrote: >> Is there a document/paper on what this is and what it's limits are etc? > > https://wiki.freebsd.org/Ports/FlavorsAndSubPackages > https://wiki.freebsd.org/Ports/FlavorsMigration > These pages don't

Re: [HEADUP] FLAVORS landing.

On 27/09/2017 07:11, Julian Elischer wrote: > Is there a document/paper on what this is and what it's limits are etc? https://wiki.freebsd.org/Ports/FlavorsAndSubPackages https://wiki.freebsd.org/Ports/FlavorsMigration Cheers, Matthew signature.asc Description: OpenPGP

Re: [HEADUP] FLAVORS landing.

Is there a document/paper on what this is and what it's limits are etc? On 26/9/17 10:05 pm, Mathieu Arnold wrote: Hi, **Do not commit FLAVORS to any ports, a hook will prevent it, that being said, do try it and test what can be done.** To test this feature in poudriere, you need