FreeBSD ports you maintain which are out of date

2020-10-17 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
+-+
deskutils/copyq | 3.12.0  | v3.13.0
+-+
devel/ahven | 2.6 | 2.8
+-+
games/lm-solve  | 0.8.4   | 0.14.2
+-+
graphics/minder | 1.11.0  | 1.11.3
+-+


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

Reported by:portscout!
___
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 PEAR ports

2020-10-17 Thread Andrea Venturoli
On 10/16/20 4:44 PM, Thierry Thomas wrote:


Are they abandoned upstream?


Some activities take place in GitHub. E.g. for MDB2 and Mail_Queue:
- https://github.com/pear/MDB2
- https://github.com/pear/Mail_Queue

but no release seem produced.


Hello and thanks for your time.

Since PEAR (or at least part of it) does not work with php74, I think 
the port infrastructure should not provide it.




Changing perspective, I guess it's time for me to remove Pear from this 
project and replace it with something else.


Use case is sending mass mail and this is achieved in two phases:
a) insert the message into a database, along with hundreds of address to 
which it must be sent;
b) periodically (currently from cron) get some of these addresses (10 to 
30) and send such messages (so they are not sent all at one time).


Anything in the port tree to achieve that?

It does not necessarily have to be PHP, as long as part A can be 
achieved/called from a PHP application in some way.



 bye & Thanks
av.
___
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: OpenJDK ports and 13-CURRENT

2020-10-17 Thread Dimitry Andric
On 10 Oct 2020, at 21:49, Shawn Webb  wrote:
> 
> On Sat, Oct 10, 2020 at 09:45:58PM +0200, Dimitry Andric wrote:
...
>> The quick way to work around these errors is to set -fcommon in CFLAGS,
>> which will basically fudge around the actual issue. The better way is to
>> get rid of the duplicated symbols. This is usually easy, except that
>> Java ports tend to take ages to build. :) I'll submit a patch when my
>> machine's finished crunching through it.
> 
> Yup. Another victim: print/tex-luatex:
> 
> https://git-01.md.hardenedbsd.org/HardenedBSD/hardenedbsd-ports/commit/229b7663bc82ff7e471dc1e19662f68d4226984a

I looked into this one finally, and it's not really an issue with any
recent clang import, as the PR is from 2018-12-20:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234221

The cause is a mixing of libstdc++ and libc++, which should not be done,
as it will almost always lead to unexpected linking errors.

The following diff fixes that:

Index: Makefile
===
--- Makefile(revision 552400)
+++ Makefile(working copy)
@@ -74,6 +74,8 @@ CONFIGURE_ARGS+=--with-system-$L \
--with-$L-include=${LOCALBASE}/include \
--with-$L-libdir=${LOCALBASE}/lib
 .endfor
+CONFIGURE_ARGS+=CC="${CC}" \
+   CXX="${CXX}"
 CPPFLAGS+= -I${LOCALBASE}/include
 MAKE_JOBS_UNSAFE=  yes
 TEX_FORMATS=   luatex


Note that the port's Makefile already has -fcommon added, to work
around duplicated symbols. Since the copy of texlive is ancient, it is
probably not worth the time to fix the actual issues.

-Dimitry



signature.asc
Description: Message signed with OpenPGP


Could a comitter take a look at new port?

2020-10-17 Thread Nuno Teixeira
Hello,

I will be very pleased if a commiter could take a look at 250426
 .
I'm very happy that (Open)Diablo2 runs nice on FreeBSD :)

Thanks very much,

Nuno Teixeira
___
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"