Unmaintained FreeBSD ports which are out of date

2024-10-08 Thread portscout
Dear port maintainers,

The portscout new distfile checker has detected that one or more
unmaintained 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. Please consider also adopting this port.
If any ports have already been updated, you can safely ignore the entry.

An e-mail will not be sent 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
+-+
devel/py-archinfo   | 9.0.5405| v9.2.122
+-+
devel/py-cle| 9.0.5405| v9.2.122
+-+
math/py-claripy | 9.0.5405| v9.2.122
+-+
security/py-ailment | 9.0.5405| v9.2.122
+-+
security/py-angr| 9.0.5405| v9.2.122
+-+
security/py-pyvex   | 9.0.5405| v9.2.122
+-+
www/groupoffice | 6.6.58  | 6.8.76
+-+


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!



ports-mgmt/portlint vs absent USE_LDCONFIG

2024-10-08 Thread Sergei Vyshenski
 Hi,

ports-mgmt/portlint-2.22.2 seems to be broken.

If a port does NOT define USE_LDCONFIG,
and this port does NOT install shared objects,
then portlint complains with:

You have defined USE_LDCONFIG, but this port does not install any shared
objects.

Example can be found here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281925

Last week line 917 of file ports-mgmt/portlint/src/portlint.pl
has been altered and now reads as follows:

if ($makevar{USE_LDCONFIG} ne "$makevar{PREFIX}/lib" && !$found_so) {

Maybe it should instead be like this:

if ($makevar{USE_LDCONFIG} ne "" && !$found_so) {

Regards, Sergei


Re: what to do about "FATAL: PLIST_FILES: files cannot contain %%FOO%% variables. Use make variables and logic instead"

2024-10-08 Thread Tatsuki Makino

Hello.

On 2024/10/09 0:16, Ronald Klop wrote:

Ok, I took a look. Does it mean just replacing %%JAVAJARDIR%% with 
${JAVAJARDIR}?


It wants to use the make variable in the outer file, so it replaces it with a 
%%FOO%% placemark.
Where a make variable can be used directly, use it directly.

I think that's what it's about.
Regards.



Re: Committer Request

2024-10-08 Thread Cy Schubert
In message <90f51caeb7ee98bf2df92a56dcd16...@chen.org.nz>, j...@chen.org.nz 
wri
tes:
> Hi,
>
> Are there any committers available to review and commit:
>   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281753
>
> Thanks!
> --
> Jonathan Chen 
>

I'll take a look.


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  https://FreeBSD.org
NTP:   Web:  https://nwtime.org

e^(i*pi)+1=0





Re: ports-mgmt/portlint vs absent USE_LDCONFIG

2024-10-08 Thread Tatsuki Makino

Hello.

I feel like it would be a good to do the following...

if ($makevar{USE_LDCONFIG} ne "") {
  if ($makevar{USE_LDCONFIG} eq "$makevar{PREFIX}/lib" && !$found_prefix_so) {
&perror("WARN", ... objects into \${PREFIX}/lib.");
  } elsif (!$found_so) {
&perror("WARN", ... objects.");
  }
}

I don't know if it is the right condition :)

Regards.


On 2024/10/09 11:52, Sergei Vyshenski wrote:

  Hi,

ports-mgmt/portlint-2.22.2 seems to be broken.

If a port does NOT define USE_LDCONFIG,
and this port does NOT install shared objects,
then portlint complains with:

You have defined USE_LDCONFIG, but this port does not install any shared
objects.

Example can be found here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281925

Last week line 917 of file ports-mgmt/portlint/src/portlint.pl
has been altered and now reads as follows:

if ($makevar{USE_LDCONFIG} ne "$makevar{PREFIX}/lib" && !$found_so) {

Maybe it should instead be like this:

if ($makevar{USE_LDCONFIG} ne "" && !$found_so) {

Regards, Sergei





Re: what to do about "FATAL: PLIST_FILES: files cannot contain %%FOO%% variables. Use make variables and logic instead"

2024-10-08 Thread Ronald Klop

Van: Piotr Smyrak 
Datum: dinsdag, 8 oktober 2024 14:48
Aan: ports@freebsd.org
Onderwerp: Re: what to do about "FATAL: PLIST_FILES: files cannot contain %%FOO%% 
variables. Use make variables and logic instead"


On Tue, 8 Oct 2024 14:34:23 +0200 (CEST)
Ronald Klop  wrote:

> I was looking for a change to devel/jna and after running portlint it
> says:
>
> FATAL: PLIST_FILES: files cannot contain %%FOO%% variables.  Use make
> variables and logic instead
>
> The lines in the Makefile this is about are:
> PLIST_FILES=%%JAVAJARDIR%%/jna-platform.jar \
> %%JAVAJARDIR%%/jna.jar
>
> What would be the proper solution for this?

See x11-fonts/iansui Makefile for an example.

HTH,
--
 Piotr Smyrak
 







Ok, I took a look. Does it mean just replacing %%JAVAJARDIR%% with 
${JAVAJARDIR}?

Rebuild the package now in poudriere and that seems to work fine.

Regards,
Ronald.


what to do about "FATAL: PLIST_FILES: files cannot contain %%FOO%% variables. Use make variables and logic instead"

2024-10-08 Thread Ronald Klop

Hi,

I was looking for a change to devel/jna and after running portlint it says:

FATAL: PLIST_FILES: files cannot contain %%FOO%% variables.  Use make variables 
and logic instead

The lines in the Makefile this is about are:
PLIST_FILES=%%JAVAJARDIR%%/jna-platform.jar \
   %%JAVAJARDIR%%/jna.jar

What would be the proper solution for this?

Regards,
Ronald.


portlint -> WARN: Makefile: a port shall not define both USE_ANT and USES[+]=gmake

2024-10-08 Thread Ronald Klop

Hi,

What is advised here?
Again about port devel/jna.

Portlint says:
WARN: Makefile: a port shall not define both USE_ANT and USES[+]=gmake

The main build uses ant and that invokes gmake. (AFAIS)
If I move gmake from USES to BUILD_DEPENDS the above WARN is gone, but now 
portlint gives me:

WARN: Makefile: dependency to gmake listed in BUILD_DEPENDS. consider using 
USES[+]=gmake.

:-)

What warning do you recommend?

Regards,
Ronald.