Re: Status of portupgrade and portmaster?

2017-09-30 Thread Mark Linimon 
On Sat, Sep 30, 2017 at 10:06:17AM -0700, Kevin Oberman wrote:
> It is unclear to me whether this was in regard to pots
> to the mailing lists or included private responses to
> the mail list discussions.

I know the former is true, not sure about the latter, but
he also used the bugs database in a fashion I can only
describe as caustic.  (That drove at least one person away
from the project.)

John is ably qualified technically.  If you agree with him
on such things as goals and design decisions, he is easy to
work with.  But my experience was that if you did not, you
were in for a long fight.

Obvious disclaimer: I was in the latter category.

People will have to come to their own conclusions.

mcl
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread Mark Linimon 
On Sat, Sep 30, 2017 at 12:30:14PM -0700, Don Lewis wrote:
> it illustrates the problem of synth being the only real
> consumer of the ADA toolchain (which John also maintained)
> on FreeBSD.

It's only fair to point out that John did a great deal of work
on Ada on FreeBSD.  However ...

> Another issue is that synth is only available on x86 because that
> is what the toolchain limits it to

This, to me, is what always stuck in my craw.

I think John may have done some work on Ada on armv6 and/or aarch64
but I would have to go check to be sure.  There is a _possibility_
that with sufficient effort it could be made to work there.  But
AFAICT there was never any realistic chance it could work on
mips,
powerpc, or sparc64.

Now, you might claim those aren't deal-breakers, but IMVHO
not
having it working on both armv6 and aarch64, at production
quality,
*is* one -- those two need to be first-class citizens going forward
(e.g. for 12.0).

mcl
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread Mark Linimon 
On Sat, Sep 30, 2017 at 10:06:17AM -0700, Kevin Oberman wrote:
> as it makes FreeBSD unusable for those of us with only "small"
> systems where the weight of poudriere simply can't be justified.

I'm confused.  I have been using poudriere for several years
to build sparc64 packages.  2 * single core 1.5GHz CPU, 16GB
RAM, 2 * 72GB SCSI-3 disks.  Yes, it can get disk-bound,
especially I am not using ZFS.  No, it's not particularly
fast.  Yes, the machine is solely dedicated to this task.

I do believe poudriere will struggle on the smaller ARM
boards, solely due to the RAM limitations.  I intend to do
some further investigation.

mcl
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread Russell L. Carter 

On 09/30/17 10:06, Kevin Oberman wrote:

On Sat, Sep 30, 2017 at 3:34 AM, Carmel NY  wrote:



[...]


As a result, I am no longer able to track HEAD and, if the issue is not
resolved in some manner before 11 support ends, will be forced to move from
FreeBSD after an using it for over 2 decades. I certainly hope that this is
not what happens.


If minimizing the size of the physical machines you have access to is
a hard constraint, then a remote binary package linux distro would
definitely decrease your pain level.  However, the trade-off is
someone else selecting your package options.  (NB: I haven't used
arch) Indeed, my disposable travel laptop is debian.  Yet I try doing
as much real work as I can on FreeBSD because the packaging system is
world class flexible.  I *loved*, possibly too much, the ability to
nuke kerberos out of my world, both base OS and packages.  Try doing
that on debian.

But FreeBSD packaging flexibility comes at a cost, and that's mainly
cpu and memory when running poudriere.  In these days of giant &&
cheap && reasonably fast USB storage, I have a hard time giving
credence to disk usage complaints.  For FreeBSD's packaging
flexibility, I am willing to invest what in real dollars is a fraction
of what we were spending in the middle '90s just to get adequate
hardware to run FreeBSD.  It really doesn't take much.  I've given
away half a dozen boxes for free to people over the last 10 years,
that would support poudriere just fine (2-4 threads, 8-16GB) because
used white boxes seem to have nearly no retrievable value.  Not an
elegant physical package like a laptop, but *who cares*.

I am piping up because when I was restarting using FreeBSD after many
years (refugee from debian), you were an invaluable source of help to
me, and of course quite a few others.  It would be sad to lose your
positive contributions to the community over this issue.

All the best,
Russell


--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread Jonathan Chen 
On 1 October 2017 at 11:29, abi  wrote:
> 30.09.2017 20:06, Kevin Oberman пишет:
>>
>>
>> As a result, I am no longer able to track HEAD and, if the issue is not
>> resolved in some manner before 11 support ends, will be forced to move
>> from
>> FreeBSD after an using it for over 2 decades. I certainly hope that this
>> is
>> not what happens.
>
>
> Is it absolutely necessary to be so overdramatic ? synth is rather young
> project and it's failure was very probable - written on long dead language
> and supported by 1 person. It can't even be replacement for portmaster as
> contains only preliminary support if port options.

What sort of port options can portmaster support better than synth?
-- 
Jonathan Chen 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread abi 

30.09.2017 20:06, Kevin Oberman пишет:


As a result, I am no longer able to track HEAD and, if the issue is not
resolved in some manner before 11 support ends, will be forced to move from
FreeBSD after an using it for over 2 decades. I certainly hope that this is
not what happens.


Is it absolutely necessary to be so overdramatic ? synth is rather young 
project and it's failure was very probable - written on long dead 
language and supported by 1 person. It can't even be replacement for 
portmaster as contains only preliminary support if port options.


You can use COMPAT11 on CURRENT as workaround for ADA issue, but this is 
a dead end anyway - synth doesn't look supported anymore, especially 
with FLAVORS on horizon.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Committer needed for [Bug 222185] devel/tig: update to 2.2.2

2017-09-30 Thread Sebastian Schwarz 
On 2017-10-01, Sebastian Schwarz wrote:
> Can some commit this to the ports tree?

Can *someone* commit this...
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Committer needed for [Bug 222185] devel/tig: update to 2.2.2

2017-09-30 Thread Sebastian Schwarz 
On 2017-09-10, bugzilla-nore...@freebsd.org wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222185
>
> Bug ID: 222185
>Summary: devel/tig: update to 2.2.2
>Product: Ports & Packages
>Version: Latest
>   Hardware: Any
> OS: Any
> Status: New
>   Severity: Affects Many People
>   Priority: ---
>  Component: Individual Port(s)
>   Assignee: freebsd-ports-b...@freebsd.org
>   Reporter: sesch...@gmail.com
> CC: darc...@gmail.com
> CC: darc...@gmail.com
>  Flags: maintainer-feedback?(darc...@gmail.com)
>
> Created attachment 186220
>   --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186220=edit
> patch
>
> tig 2.2.2 was released in May:
> https://github.com/jonas/tig/releases/tag/tig-2.2.2
>
> The attached patch updates the port to that version.

Can some commit this to the ports tree?  There has been no
response from the maintainer in three weeks.  The patch is a
simple version bump.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread Kurt Jaeger 
Hi!

> "small" systems where the weight poudriere simply can't be justified. (I
> have no system with other than SATA disk drives and, for my current needs,
> 1 TB of SATA on my development system and .5TB on my production system is
> adequate. Both systems are physically constrained in expansion capability,
> though otherwise easily meet my requirements.

My poudriere builder has 10 jails

103 10.3-RELEASE amd64
10i 10.3-RELEASE-p17 i386
11a 11.0-RELEASE-p1 amd64
11i 11.0-RELEASE-p1 i386
111 11.1-RELEASE amd64
cur 12.0-CURRENT 1200035
arm6 12.0-CURRENT r306902
p64 12.0-CURRENT r306902
93a 9.3-RELEASE-p48 amd64
93i 9.3-RELEASE-p48 i386

and it uses up approx. 3 GB of disk space.

The ports distfiles are using up approx. 16 GB of disk space.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread Don Lewis 
On 30 Sep, Kevin Oberman wrote:

> John did state that he would continue to support synth. I can't say if he
> has continued to make contributions. In any case, only poudriere is
> available for maintaining ports in HEAD and I, for one, feel that it is
> simply unacceptable as it make FreeBSD unusable for those of us with only
> "small" systems where the weight poudriere simply can't be justified. (I
> have no system with other than SATA disk drives and, for my current needs,
> 1 TB of SATA on my development system and .5TB on my production system is
> adequate. Both systems are physically constrained in expansion capability,
> though otherwise easily meet my requirements.

1 TB should be plenty-o-room for poudriere in most cases.  The machine I
use for building packages only has a mirrored pair of 1TB Western
Digital Green drives that were purchased years ago for another project
where they were eventually replaced, so I just happened to have them
handy when I put my package builder together.  I use that box to build a
set of about 1800 ports for FreeBSD 10 i386,  FreeBSD 11 amd64, FreeBSD
11 i386, and FreeBSD 12 amd64.  There are some of the larger ports in
that set, like chromium, firefox, thunderbird, openoffice-4,
openoffice-devel, and libreoffice.  I also run the other supported
release / x86 combinations when I'm doing port testing.

%zpool list
NAMESIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
zroot   888G   608G   280G -64%68%  1.00x  ONLINE  -

The biggest consumer of space is actually my collection of VM images
that get used when this machine isn't building packages.

My biggest constraint is CPU cycles.  I/O is generally not a problem
because I was able to max out RAM in this machine and use tmpfs for most
things in poudriere.

Centralizing port building like this allows me to continue to use some
really ancient and slow hardware, like my 2003 vintage laptop that only
has a 160 GB drive that is split between both Windows and FreeBSD and
1 GB of RAM.  It's still perfectly adequate for light use running a
browser and editing documents with one of the office products, but
trying to build those ports on it is totally out of the question.  I
also have a Via C3 machine with only 256 MB of RAM that I use as a
lightweight server and I maintain using the packages produced by
poudriere.  This also allows me to avoid bogging down my daily desktop
machine with port builds.  It's somewhat more modern, but a big batch of
port builds would probably make it really laggy for a long period of
time.

That said, if you only have one machine, synth is probably a better
choice.

The situation on 12.0 should be fixable by someone with the proper
skillset, but it illustrates the problem of synth being the only real
consumer the ADA toolchain (which John also maintained) on FreeBSD.
Basically we've got an important tool that had a single point of
failure, and even without the the politics, we'd be in the same
situation if John had been run over by a bus.  By contrast, poudriere
is mostly shell scripts, which makes me shudder for totally different
reasons.

Another issue is that synth is only available on x86 because that what
the toolchain limits it to, so that leaves the our other architectures
out in the cold.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD telldusd port fix for devd script

2017-09-30 Thread Hans Petter Selasky 

Hi Johan,

The following devd script is not fully correct.


--- tdadmin/freebsd-devd-tellstick.conf 2014-04-06 22:40:11.0 +0200
+++ tdadmin/freebsd-devd-tellstick.conf 2014-04-06 20:37:50.501751596 +0200
@@ -0,0 +1,12 @@
+attach 10 {
+   device-name "uftdi[0-9]+";
+   match "vendor" "0x1781";
+   match "product" "0x0c30";
+
+   action "chgrp dialer /dev/ugen$port.$devaddr; chmod 660 
/dev/ugen$port.$devaddr;
+   @CMAKE_INSTALL_PREFIX@/sbin/tdadmin --pid $product --vid $vendor 
--serial $sernum controller connect";
+};


It should be:

notify 10 {
match "system" "USB";
match "subsystem" "DEVICE";
match "type" "ATTACH";
match "vendor" "0x1781";
match "product" "0x0c30";
	action "chgrp dialer /dev/$cdev; chmod 660 /dev/$cdev 
@CMAKE_INSTALL_PREFIX@/sbin/tdadmin --pid $product --vid $vendor 
--serial $sernum controller connect";

}

Can you test and update the port in FreeBSD ?

Thank you!

--HPS
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Giving up maintainership

2017-09-30 Thread Henk van Oers 


Please see:

http://portscout.freebsd.org/hvo...@xs4all.nl.html

Thank you,
Henk
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread Carmel NY 
On Sat, 30 Sep 2017 10:06:17 -0700, Kevin Oberman stated:

>On Sat, Sep 30, 2017 at 3:34 AM, Carmel NY  wrote:
>
>>
>> Excuse my ignorance, but why was John Marino exiled?
>>
>>  
>Not to state any opinion of my own, but John had his commit bit pulled
>after a long mail dialog about the utility of synth as a complete
>replacement for all older port updating tools save poudriere. It was
>claimed that John's messages were abusive and in violation of the FreeBSD
>"Code of Conduct". It is unclear to me whether this was in regard to pots
>to the mailing lists or included private responses to the mail list
>discussions.
>
>Core reviewed the messages and agreed that they were unacceptable. John
>disagreed and declined to retract his statements, so Core voted to withdraw
>his commit bit.
>
>The public details are available in the mail archives.
>
>John did state that he would continue to support synth. I can't say if he
>has continued to make contributions. In any case, only poudriere is
>available for maintaining ports in HEAD and I, for one, feel that it is
>simply unacceptable as it make FreeBSD unusable for those of us with only
>"small" systems where the weight poudriere simply can't be justified. (I
>have no system with other than SATA disk drives and, for my current needs,
>1 TB of SATA on my development system and .5TB on my production system is
>adequate. Both systems are physically constrained in expansion capability,
>though otherwise easily meet my requirements.
>
>As a result, I am no longer able to track HEAD and, if the issue is not
>resolved in some manner before 11 support ends, will be forced to move from
>FreeBSD after an using it for over 2 decades. I certainly hope that this is
>not what happens.

I could not agree more. If this matter is not resolved before FBSD 12 is
released, I will have to start looking for a replacement for FBSD.

-- 
Carmel
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

databases/p5-Dancer2-Plugin-DBIC maintainer transfer

2017-09-30 Thread Henk van Oers 


I want to transfer maintainership.

I am not a user of this port.

-- Forwarded message -- Date: Sat, 30 Sep 2017 08:17:20 
[...]

Port| Current version | New version
+-+
databases/p5-Dancer2-Plugin-DBIC| 0.0013  | 0.0100
+-+
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread Kevin Oberman 
On Sat, Sep 30, 2017 at 3:34 AM, Carmel NY  wrote:

>
> Excuse my ignorance, but why was John Marino exiled?
>
>
Not to state any opinion of my own, but John had his commit bit pulled
after a long mail dialog about the utility of synth as a complete
replacement for all older port updating tools save poudriere. It was
claimed that John's messages were abusive and in violation of the FreeBSD
"Code of Conduct". It is unclear to me whether this was in regard to pots
to the mailing lists or included private responses to the mail list
discussions.

Core reviewed the messages and agreed that they were unacceptable. John
disagreed and declined to retract his statements, so Core voted to withdraw
his commit bit.

The public details are available in the mail archives.

John did state that he would continue to support synth. I can't say if he
has continued to make contributions. In any case, only poudriere is
available for maintaining ports in HEAD and I, for one, feel that it is
simply unacceptable as it make FreeBSD unusable for those of us with only
"small" systems where the weight poudriere simply can't be justified. (I
have no system with other than SATA disk drives and, for my current needs,
1 TB of SATA on my development system and .5TB on my production system is
adequate. Both systems are physically constrained in expansion capability,
though otherwise easily meet my requirements.

As a result, I am no longer able to track HEAD and, if the issue is not
resolved in some manner before 11 support ends, will be forced to move from
FreeBSD after an using it for over 2 decades. I certainly hope that this is
not what happens.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread RW via freebsd-ports 
On Sat, 30 Sep 2017 10:34:11 +
Carmel NY wrote:


> I have just the opposite experience. With "portupgrade" I was getting
> all too many dependencies installed that I had no use for. I
> personally appreciate synth's finer-grain installation philosophy.

But presumably that's just portupgrade installing build dependencies
and not removing them automatically.  
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread Carmel NY 
On Sat, 30 Sep 2017 09:27:40 +, Thomas Mueller stated:

>from Chris H:
>
>> FWIW I loved portmaster, but quickly found that by choosing it, I was
>> *instantly* at odds with a large majority of the FreeBSD crowd.
>> Eventually, I experimented with other choices, and finally landed on
>> ports-mgmt/synth, and never looked back. Like Carmel, I found some aspects
>> un-intuitive. But after figuring them out. I was hooked. John Marino did
>> a wonderful job on this, and is very helpful.  
>
>On one computer (motherboard MSI Z68MA-ED55(B3)), synth works great, as long
>as I avoid the options dialog and put the options
>in /usr/local/etc/synth/LiveSystem-make.conf

I have learned to put needed options in the "LiveSystem-make.conf" file. I
don't consider it a hindrance although others might.

>But there is the annoyance that many useful dependencies are not installed
>unless I type the command to install those already-built packages.

I have just the opposite experience. With "portupgrade" I was getting all too
many dependencies installed that I had no use for. I personally appreciate
synth's finer-grain installation philosophy. Perhaps an option to install
"ALL" dependencies could be added to synth's list of options. It is above my
pay grade.

>On the other computer, motherboard MSI Z77 MPOWER, same FreeBSD version,
>11.1-STABLE, synth fails most of the time and usually crashes.

Sorry, but I don't know enough about mother boards to be of any help to you
here. What is the error message and what does the log say about it?

>I believe John Marino is unfortunately banished from FreeBSD but might still
>be active with DragonFlyBSD.

Excuse my ignorance, but why was John Marino exiled?

>from Matt Smith:
>
>> I agree. Portmaster was useful for many years but these days it is being
>> left behind. The expectation is that ports are built in a clean room
>> environment and portmaster does not provide that. I used synth for several
>> months and it is a great tool. It works fine, but my problem with it is
>> that the developer was forced out of FreeBSD and it needs an ada compiler.  
>
>> I think on FreeBSD 12 the ada compiler is broken isn’t it? Meaning synth
>> will break. For this reason I switched to poudriere and that works fine for
>> me. As that is the tool used by the pkg builders themselves I know it will
>> work.  

I can see this as an excellent excuse NOT to update to the FreeBSD 12 when it
is officially released.
 
>> For example we are shortly getting flavors support in the ports tree. I
>> think the author of synth has already said he is not going to support this
>> whereas poudriere will straight away.  
>
>Building synth requires gcc6-aux, but gcc5-aux and gcc6-aux would not build
>following the introduction of ino64.
>
>I don't know if that has been fixed.
>
>John Marino attempted to port synth to NetBSD with pkgsrc, but last time I
>looked, gcc6-aux is broken on NetBSD, Makefile says so.
>
>Tom
>

-- 
Carmel
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of portupgrade and portmaster?

2017-09-30 Thread Thomas Mueller 
from Chris H:

> FWIW I loved portmaster, but quickly found that by choosing it, I was
> *instantly* at odds with a large majority of the FreeBSD crowd.
> Eventually, I experimented with other choices, and finally landed on
> ports-mgmt/synth, and never looked back. Like Carmel, I found some aspects
> un-intuitive. But after figuring them out. I was hooked. John Marino did
> a wonderful job on this, and is very helpful.

On one computer (motherboard MSI Z68MA-ED55(B3)), synth works great, as long as 
I avoid the options dialog and put the options in 
/usr/local/etc/synth/LiveSystem-make.conf

But there is the annoyance that many useful dependencies are not installed 
unless I type the command to install those already-built packages.

On the other computer, motherboard MSI Z77 MPOWER, same FreeBSD version, 
11.1-STABLE, synth fails most of the time and usually crashes.

I believe John Marino is unfortunately banished from FreeBSD but might still be 
active with DragonFlyBSD.

from Matt Smith:

> I agree. Portmaster was useful for many years but these days it is being left
> behind. The expectation is that ports are built in a clean room environment
> and portmaster does not provide that. I used synth for several months and it
> is a great tool. It works fine, but my problem with it is that the developer
> was forced out of FreeBSD and it needs an ada compiler.

> I think on FreeBSD 12 the ada compiler is broken isn’t it? Meaning synth 
> will
> break. For this reason I switched to poudriere and that works fine for me. As
> that is the tool used by the pkg builders themselves I know it will work.

> For example we are shortly getting flavors support in the ports tree. I think
> the author of synth has already said he is not going to support this whereas
> poudriere will straight away.

Building synth requires gcc6-aux, but gcc5-aux and gcc6-aux would not build 
following the introduction of ino64.

I don't know if that has been fixed.

John Marino attempted to port synth to NetBSD with pkgsrc, but last time I 
looked, gcc6-aux is broken on NetBSD, Makefile says so.

Tom

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

2017-09-30 Thread portscout 
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, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
net/openvswitch | 2.3.3   | 2.8.1
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"