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: HEADSUP: FLAVORS (initial version) and subpackages proposals

2016-12-19 1:31 GMT+01:00 Baptiste Daroussin : > Hi all, > > I have been working for a while on 2 long standing feature request for the > ports > tree: flavors and subpackages. > > For flavors I would like to propose a simple approach first which is more > like a > rework of

Re: The ports collection has some serious issues

2016-12-18 21:22 GMT+01:00 Kevin Oberman : > synth(8)... try it, you'll like it. (Sorry, dating myself.) I also never tried synth as I'm very familiar with poudriere, but I'll have a look for sure :) -- Demelier David ___

Re: The ports collection has some serious issues

On 2016-Dec-17 20:16:12 -0600, John Marino wrote: >On 12/17/2016 19:35, Peter Jeremy wrote: >> $ cd /usr/ports/ports-mgmt/synth/ && make >> [ about an hour of grinding away elided ] >> ===> ini_file_manager-03_2 depends on file: /usr/local/gcc6-aux/bin/ada - >> not

Re: The ports collection has some serious issues

On 12/18/2016 02:24 AM, John Marino wrote: 2) portmaster's dirty build method is inferior to clean environment builds (true) 3) There is better and official alternative (true) Maybe. I have a case where portmaster (on my current production box) builds fine but poudriere (on my intended

HEADSUP: FLAVORS (initial version) and subpackages proposals

Hi all, I have been working for a while on 2 long standing feature request for the ports tree: flavors and subpackages. For flavors I would like to propose a simple approach first which is more like a rework of the slave ports for now: Examples available here: https://reviews.freebsd.org/D8840

Re: graphics/Inkscape not building either with or without openmp option set

2016-12-18 21:44 GMT+01:00 Kevin Oberman : > On Sun, Dec 18, 2016 at 12:22 PM, Fernando Herrero Carrón < > elfe...@gmail.com> wrote: > >> 2016-12-18 21:19 GMT+01:00 Fernando Herrero Carrón : >> >> > >> > It looks like inkscape unconditionally asks for

Re: graphics/Inkscape not building either with or without openmp option set

On Sun, Dec 18, 2016 at 12:22 PM, Fernando Herrero Carrón wrote: > 2016-12-18 21:19 GMT+01:00 Fernando Herrero Carrón : > > > > > It looks like inkscape unconditionally asks for compiler:openmp in its > > Makefile. > > > > Sorry, I just rechecked and this

Re: graphics/Inkscape not building either with or without openmp option set

2016-12-18 21:22 GMT+01:00 Fernando Herrero Carrón : > > > 2016-12-18 21:19 GMT+01:00 Fernando Herrero Carrón : > >> >> It looks like inkscape unconditionally asks for compiler:openmp in its >> Makefile. >> > > Sorry, I just rechecked and this is not true.

Re: graphics/Inkscape not building either with or without openmp option set

2016-12-18 21:19 GMT+01:00 Fernando Herrero Carrón : > > It looks like inkscape unconditionally asks for compiler:openmp in its > Makefile. > Sorry, I just rechecked and this is not true. Still, it fails in both cases. ___

graphics/Inkscape not building either with or without openmp option set

Hi everyone, graphics/inkscape is failing to build with openmp otion set, but unchecking it yields exactly the same result. There is an open PR about this ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208883) but hasn't receive much attention. It looks like inkscape unconditionally asks

Re: The ports collection has some serious issues

On Sun, 18 Dec 2016, Willem Jan Withagen wrote: On 18-12-2016 16:00, John Marino wrote: [please keep me CC'd, I can't respond easily if not] I find that sort of strange... but that could be my feeling. Given the hyperbole and intentionally misleading content of waay too much of this thread,

Re: The ports collection has some serious issues

On 18-12-2016 16:00, John Marino wrote: > [please keep me CC'd, I can't respond easily if not] I find that sort of strange... but that could be my feeling. Someone builds a tool, and then decides that it is not very useful to be part of the community that he creates the tool for... Like I

Re: The ports collection has some serious issues

On Sun, 18 Dec 2016, John Marino wrote: > > > Real smooth there, Slick. > > > > Sarcasm might get you somewhere, but I'm not sure you want to be > > there. > > He was trolling. You know it. I know it. Everyone that read it knows it. I happen to know Peter as a friend; you don't. He doesn't

Re: The ports collection has some serious issues

On 18/12/2016 14:18, Grzegorz Junka wrote: > Isn't poudriere automatically saving the options file when building a > new port with default options (i.e. when no options have been > specified)? And also, aren't the selected options available in the > resulted pkg file, so that synth could look them

Re: The ports collection has some serious issues

On 17 Dec 2016, at 20:47, Alphons van Werven wrote: > But ever >> since some time during the 9.X era I started to pick up signs that the >> FreeBSD project as a whole is moving into a direction that troubles me--in >> some cases deeply indeed. I don't know what direction

The ports collection has some serious issues

Grzegorz Junka wrote: On 17/12/2016 18:51, John Marino wrote: On 12/17/2016 12:34, abi wrote: 2. It doesn't provide dialog for port options, so 2.1 I don't receive information if port options have changed. I don't know what else will be pulled to my system after port tree update. which of

Re: VCode on FreeBSD?

I did tried it months ago. It needed special version of npm and such packages that some of them didn't met of what we had on port-tree. I didn't spend more time after that though (But I guess it was possible to satisfy it with little patches). === Best wishes, Mokhi.

Re: The ports collection has some serious issues

On 17/12/2016 18:51, John Marino wrote: On 12/17/2016 12:34, abi wrote: 2. It doesn't provide dialog for port options, so 2.1 I don't receive information if port options have changed. I don't know what else will be pulled to my system after port tree update. which of course is a false

VCode on FreeBSD?

Are there any objective reasons why Visual Studio Code hasn't been ported to FreeBSD yet (apart from not having the time/person to do it)? Grzegorz ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To

Re: The ports collection has some serious issues

On 12/18/16 02:24, John Marino wrote: The whole "see, it's not a replacement, you lose" tactic is weak and transparent. Nobody ever said that. what was said: 1) portmaster is not maintained (true) 2) portmaster's dirty build method is inferior to clean environment builds (true) 3) There is

The ports collection has some serious issues

David wrote On 12/16/2016 04:06 PM, John Marino wrote: Starting with a clean system: 1) install synth from binary package from official freebsd builder (a single package) What about just building synth from ports? Then the OP have everything built from ports. -- David In the example, the

new multimedia/motion problem

Hi! New motion-4.0.1 Trying to run a web interface results in an error: [0:] [NTC] [ALL] [Dec 18 20:49:58] motion_startup: Using log type (ALL) log level (ALL) [0:] [NTC] [ENC] [Dec 18 20:49:58] ffmpeg_init: ffmpeg libavcodec version 57.64.101 libavformat version 57.56.100 [0:] [NTC] [ALL] [Dec

Re: Dropping enigmail support from enigmail

## Martin Birgmeier (la5lb...@aon.at): > However, lightning seems to be gone - I don't find it installed with the > port and it does not seem to be offered as an add-on for this platform. I believe thunderbird by default activated the "wrong" lightning plugin (the one which was now removed) and

Re: The ports collection has some serious issues

On 12/16/2016 04:06 PM, John Marino wrote: Starting with a clean system: 1) install synth from binary package from official freebsd builder (a single package) What about just building synth from ports? Then the OP have everything built from ports. -- David

Re: The ports collection has some serious issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 18 Dec 2016 17:43:32 +1100 Greg 'groggy' Lehey wrote: > On Saturday, 17 December 2016 at 20:16:12 -0600, John Marino wrote: > > On 12/17/2016 19:35, Peter Jeremy wrote: > >> $ cd /usr/ports/ports-mgmt/synth/ && make >

Re: Dropping enigmail support from enigmail

Thanks for the pointer to enigmail in UPDATING, so I misunderstood the log message and should have looked in UPDATING. However, lightning seems to be gone - I don't find it installed with the port and it does not seem to be offered as an add-on for this platform. On 12/17/16 23:09, Jan Beich

Using the license framework to define a port with distribution restrictions

Hi, I have a question in relation to the FreeBSD license framework and how to define a port with distribution restrictions. The port in question is devel/vasm port. The legal section of documentation (1.2) for this port is at: http://sun.hasenbraten.de/vasm/release/vasm.html It is not clear

Re: The ports collection has some serious issues

>From John Marino and my previous post: > > I believe you could cd $PORTSDIR/ports-mgmt/synth and > > make package-recursive |& tee build-12amd64.log (or whatever you want to > > name the log file; this example if for shell tcsh)? > That installs build dependencies on the system. That would be