Unmaintained FreeBSD ports which are out of date

2024-10-05 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
+-+
graphics/aloadimage | 0.6.3.3 | 0.6.3.4
+-+
japanese/mecab-ipadic-utf8  | 2.7.0-20070801  | 
4.0.0-
+-+
multimedia/arcan| 0.6.3.3 | 0.6.3.4
+-+
security/gokey  | 0.1.2   | v0.26.0
+-+


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!



Update and merge mail/mu and mail/mu4e

2024-10-05 Thread RwN

Hi,

I send you an email to ask a review for an update to mail/mu at 
https://reviews.freebsd.org/D46961


It is my first time to deal with port.

Let me introduce few context about this review.

- mail/mu is a tool to manage maildir. Its frontend is mail/mu4e 
 for emacs. Actually freebsd ports has both ports.


- I contact the ports maintainer, by mail, by reporting a bug at 
 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280678 and a 
 previous review at   https://reviews.freebsd.org/D45539 without 
 any  response.


- My review consist in an urgent up-to-date and merging mail/mu 
 and mail/mu4e, the latter becomes a build option (activated by 
 default) because the developpment of both packages are 
 intimately  construct as well as in the default building system 
 (meson).


- Note, I was unable to use USES += emacs which yields an a ninja 
 error thus I pu in in  BUILD_DEPENDS.


My questions are:

- What do you think of merging both package ?

- Can you review the code ?

Any comments is welcome!

Best,
RwN.