FreeBSD ports you maintain which are out of date

2021-11-09 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/remotebox   | 2.7 | 2.8
+-+


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!



Re: What to do with the "Created by" header comments?

2021-11-09 Thread Luca Pizzamiglio
Hi Mel,

IIRC the "# Created by: ..." line was added to give credits to the original
creator of the port.
I'm not sure if this is still a thing.

Best regards,
pizzamig



On Mon, Nov 8, 2021 at 9:28 PM Mel Pilgrim 
wrote:

> In a port I recently submitted, I included the "# Created by: ..." line
> at the top of the Makefile I had seen in other ports.  When the port was
> committed, that line was excluded.
>
> Should I strip this line from ports I maintain as I update them, or let
> it sit until a committer does a tree-wide removal?
>
>


Re: What to do with the "Created by" header comments?

2021-11-09 Thread Guido Falsi

On 09/11/21 16:33, Luca Pizzamiglio wrote:

Hi Mel,

IIRC the "# Created by: ..." line was added to give credits to the original
creator of the port.
I'm not sure if this is still a thing.



As far as I remember (please correct me if I'm wrong) it's deprecated 
and should not be added to newly created ports, also because the 
information is easy to find in the repo history.


I don't think there is any rule for existing ones, I personally leave 
them there unless requested to do anything different.


--
Guido Falsi 



Request for BubbleUPnP Server

2021-11-09 Thread Nicolas Boisvert

Hello all,

There is an install for Linux (.db), one for Synology and one for Java.

Can requests be made in this mailing list?

https://www.bubblesoftapps.com/bubbleupnpserver2/docs/linux_install.html





Re: Request for BubbleUPnP Server

2021-11-09 Thread Guangyuan Yang
Nicolas Boisvert  于2021年11月9日周二 下午2:44写道:
>
> Hello all,
>
> There is an install for Linux (.db), one for Synology and one for Java.
>
> Can requests be made in this mailing list?
>
> https://www.bubblesoftapps.com/bubbleupnpserver2/docs/linux_install.html
>
>
>

Hi,

Please feel free to open a bug report at
https://bugs.freebsd.org/bugzilla/. On a quick look, the porting of
this software should be doable.

Best,

-- 
Guangyuan Yang
y...@freebsd.org



HEADS UP: intent to merge clang/llvm 13.0.0 the coming weekend

2021-11-09 Thread Dimitry Andric
Hi,

This is a heads-up so that you are aware I'm intending to merge
clang/llvm 13.0.0 the coming weekend, e.g. somewhere between Sat
2021-11-13 and Sun 2021-11-14. The source of the merge will be
,
which I regularly sync up with our main branch.

I think most of the important ports issues found via the exp-run bug
(https://bugs.freebsd.org/258209) are now ironed out, but if you have
suggestions for ones that have failed in the exp-run but are not fixed
yet, and are important to you, please submit feedback on the bug. (Or
create a new bug and link it.)

Also, if there are other reasons to postpone the merge, please let me
know.

-Dimitry



signature.asc
Description: Message signed with OpenPGP


Running php-composer as part of a build process

2021-11-09 Thread Mel Pilgrim
I'm porting a PHP application that uses composer[1] to download and 
manage what effectively becomes locally-bundled contrib.


Doing this during the build process isn't an option because it creates a 
nightmare of licensing and version management. Also, composer needs 
internet access and can be configured to do other things, like code 
compliance and unit tests.


Can I run something like composer from the post-install target?  Is it 
reasonable to assume internet access is available during port/pkg install?


1: https://getcomposer.org/