Re: port files/patch-*: PREFIX or LOCALBASE

[Nuno Teixeira]

(...)

# PREFIX- Where *this* port installs its files.
# Default: ${LINUXBASE} if USE_LINUX_PREFIX
is set,
# otherwise ${LOCALBASE}

# LOCALBASE - Where ports install things.
# Default: /usr/local

Nuno Teixeira  escreveu no dia quarta, 19/05/2021 à(s)
09:42:

> Hello,
>
> I'm working in a port that have several files/patches like:
>
> --- NsCDE/bin/nscde.orig2021-05-02 07:33:53 UTC
> +++ NsCDE/bin/nscde
> @@ -42,16 +42,11 @@ fi
>  # Set main NSCDE and FVWM variables. Most of the things later
>  # depends on this core variables.
>  export FVWM_USERDIR="${HOME}/.NsCDE"
> -export NSCDE_ROOT=/opt/NsCDE
> -export FVWM_DATADIR="${NSCDE_ROOT}/config"
> +export NSCDE_ROOT=/usr/local
> +export FVWM_DATADIR="/usr/local/etc/nscde"
> (...)
>
> What is more correct to substitute "/usr/local" as variable?
> ${PREFIX} or ${LOCALBASE}?
>
> Thanks in advance,
> eduardo
>
___
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"

port files/patch-*: PREFIX or LOCALBASE

[Nuno Teixeira]

Hello,

I'm working in a port that have several files/patches like:

--- NsCDE/bin/nscde.orig2021-05-02 07:33:53 UTC
+++ NsCDE/bin/nscde
@@ -42,16 +42,11 @@ fi
 # Set main NSCDE and FVWM variables. Most of the things later
 # depends on this core variables.
 export FVWM_USERDIR="${HOME}/.NsCDE"
-export NSCDE_ROOT=/opt/NsCDE
-export FVWM_DATADIR="${NSCDE_ROOT}/config"
+export NSCDE_ROOT=/usr/local
+export FVWM_DATADIR="/usr/local/etc/nscde"
(...)

What is more correct to substitute "/usr/local" as variable?
${PREFIX} or ${LOCALBASE}?

Thanks in advance,
eduardo
___
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: FreeBSD Manual Pages site: missing manuals

[Nuno Teixeira]

Thanks Makino!

It makes sense and my investigation is over :)

Thanks,

Nuno Teixeira

Tatsuki Makino  escreveu no dia segunda,
5/04/2021 à(s) 05:25:

> probably
>
> "releng/12.2" branch: Thu Sep 10 23:56:59 2020 UTC
> Add gitup 0.87: Tue Dec 29 12:53:20 2020 UTC
>
>
___
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 Manual Pages site: missing manuals

[Nuno Teixeira]

 Hello,

I have an interesting PR
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254759> saying that
FreeBSD Manual Pages site
<https://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+12.2-RELEASE+and+Ports>
can't find gitup (ports) manpage.
It also couldn't find gopass (ports).

Any hints why this happening?

Thanks,

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"

Re: passing Makefile targets to a go port

[Nuno Teixeira]

It seams that GO_BUILDFLAGS is the way to go to add additional targets but
I couldn't found any examples and I don't know the correct syntax to use

Nuno Teixeira  escreveu no dia domingo, 14/03/2021
à(s) 11:37:

> GO_BUILDFLAGS
>
> Additional build arguments to be passed to go build.
>
> Nuno Teixeira  escreveu no dia domingo, 14/03/2021
> à(s) 11:30:
>
>> Hello,
>>
>> I'm working on updating security/gopass.
>>
>> New version added a gopass.1 man file but it is needed to run "gmake man"
>> in WRKSRC.
>> How do I pass "gmake man" to go port Makefile?
>>
>> In the other hand, this port uses a:
>> ---
>> post-build:
>> .for SHELL in bash fish zsh
>> ${GO_WRKDIR_BIN}/${PORTNAME} completion ${SHELL} >
>> ${WRKSRC}/${SHELL}
>> .endfor
>> ---
>> to create completion files, and it can be accomplished with "gmake
>> completion" at WRKSRC.
>>
>> It was cool that it is a way to add "completion" and "man" targets to
>> gopass port.
>>
>> gopass Makefile <https://github.com/gopasspw/gopass/blob/master/Makefile>
>>
>> Cheers,
>> 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"

Re: passing Makefile targets to a go port

[Nuno Teixeira]

GO_BUILDFLAGS

Additional build arguments to be passed to go build.

Nuno Teixeira  escreveu no dia domingo, 14/03/2021
à(s) 11:30:

> Hello,
>
> I'm working on updating security/gopass.
>
> New version added a gopass.1 man file but it is needed to run "gmake man"
> in WRKSRC.
> How do I pass "gmake man" to go port Makefile?
>
> In the other hand, this port uses a:
> ---
> post-build:
> .for SHELL in bash fish zsh
> ${GO_WRKDIR_BIN}/${PORTNAME} completion ${SHELL} >
> ${WRKSRC}/${SHELL}
> .endfor
> ---
> to create completion files, and it can be accomplished with "gmake
> completion" at WRKSRC.
>
> It was cool that it is a way to add "completion" and "man" targets to
> gopass port.
>
> gopass Makefile <https://github.com/gopasspw/gopass/blob/master/Makefile>
>
> Cheers,
> 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"

passing Makefile targets to a go port

[Nuno Teixeira]

Hello,

I'm working on updating security/gopass.

New version added a gopass.1 man file but it is needed to run "gmake man"
in WRKSRC.
How do I pass "gmake man" to go port Makefile?

In the other hand, this port uses a:
---
post-build:
.for SHELL in bash fish zsh
${GO_WRKDIR_BIN}/${PORTNAME} completion ${SHELL} >
${WRKSRC}/${SHELL}
.endfor
---
to create completion files, and it can be accomplished with "gmake
completion" at WRKSRC.

It was cool that it is a way to add "completion" and "man" targets to
gopass port.

gopass Makefile <https://github.com/gopasspw/gopass/blob/master/Makefile>

Cheers,
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"

Re: On 14-CURRENT: no ports options anymore?

[Nuno Teixeira]

I have same problem days ago when dialog4ports crashed.

just reinstall/install ports-mgmt/dialog4ports/

Hartmann, O.  escreveu no dia sábado, 13/03/2021
à(s) 19:17:

> Since I moved on to 14-CURRENT, I face a very strange behaviour when
> trying to set
> options via "make config" or via poudriere accordingly. I always get "===>
> Options
> unchanged" (when options has been already set and I'd expect a dialog
> menu).
> This misbehaviour is throughout ALL 14-CURRENT systems (the oldest is at
> FreeBSD
> 14.0-CURRENT #49 main-n245422-cecfaf9bede9: Fri Mar 12 16:08:09 CET 2021
> amd64).
>
> I do not see such a behaviour with 13-STABLE, 12-STABLE, 12.2-RELENG.
>
> How to fix this? What happened?
>
> Thanks in advance,
>
> O. Hartmann
>
___
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"

port that needs go >= 1.16

[Nuno Teixeira]

Hello!

I'm testing updating security/gopass
<https://www.freshports.org/security/gopass/> to latest version and it
fails compiling because it need go lang >= 1.16, and mine is 1.15.8.

How to "force" port makefile to use >= 1.16
Do I need to do that? Since 1.16 is available now on ports?

https://github.com/gopasspw/gopass/issues/1804

Thanks,

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"

NLS knob: need help (and hacking)

[Nuno Teixeira]

Hello,

I've updated gbrainy <https://www.freshports.org/games/gbrainy/> to last
version and it solves DEPRECATED: PR 253058
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253058>

This program doesn't respect NLS knob (6.7.2. Optional Usage, Porter's
Handbook).

Could anyone try it to find a way to make NLS knob works? Gnu configure
have --disable-nls in it, but I can't make it to work.

//
- I contacted author and asked for his help on this matter.
- Author replied:
"Why do you need --disable-nls? How this helps in FreeBSD?
I'm surprised that this is needed since it's not needed for other Unix
variants. Additionally I have not made any major change in the last years
and I understand there was already a FreeBSD build."
- What should I reply?
//

Thanks,

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"

Need a nice committer on graphics/mtpaint

[Nuno Teixeira]

Hello,

10 years later, a new version?
I like it because of that.

Hope I didn't ruined 252926
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252926>

Thanks :)

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"

Re: MASTER_SITES=GH? like SF

[Nuno Teixeira]

Thanks for clarification.

Nuno

Mathieu Arnold  escreveu no dia segunda, 18/01/2021 à(s)
10:37:

> On Mon, Jan 18, 2021 at 07:32:46AM +0000, Nuno Teixeira wrote:
> > Hello,
> >
> > I will use graphics/glfw port as an example:
> >
> > MASTER_SITES= SF
> >
> > The project moved to github so I will prefer use GH releases instead of
> SF:
> >
> > MASTER_SITES=
> https://github.com/glfw/glfw/releases/download/${PORTVERSION}/
> > works ok.
> >
> > MASTER_SITES= GH:
>
> Remove the `:`.  Also, GH should never be used by itself, it is only
> there as an artefact of the way USE_GITHUB works.  But if there is a
> released tarball as you indicate up there, you should use it.
>
> > => glfw-3.3.2.zip doesn't seem to exist in /work/DISTFILES/.
> > ===> /!\ Error /!\
> >  The :DEFAULT group used for glfw-3.3.2.zip is missing
> >  from MASTER_SITES. Check for typos, or errors.
> > *** Error code 1
> >
> > Thanks,
> >
> > 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"
> >
>
> --
> Mathieu Arnold
>
___
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"

MASTER_SITES=GH? like SF

[Nuno Teixeira]

Hello,

I will use graphics/glfw port as an example:

MASTER_SITES= SF

The project moved to github so I will prefer use GH releases instead of SF:

MASTER_SITES=https://github.com/glfw/glfw/releases/download/${PORTVERSION}/
works ok.

MASTER_SITES= GH:

=> glfw-3.3.2.zip doesn't seem to exist in /work/DISTFILES/.
===> /!\ Error /!\
 The :DEFAULT group used for glfw-3.3.2.zip is missing
 from MASTER_SITES. Check for typos, or errors.
*** Error code 1

Thanks,

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"

Re: Need a commiter

[Nuno Teixeira]

and 252740 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252740> :)

Nuno Teixeira  escreveu no dia sábado, 16/01/2021
à(s) 12:08:

> Hello,
>
> Could a commiter take a look at:
>
> 252635 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252635>
> 252601 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252601>
> 251917 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251917>
>
> Thank you!
>
> 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"

Need a commiter

[Nuno Teixeira]

Hello,

Could a commiter take a look at:

252635 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252635>
252601 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252601>
251917 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251917>

Thank you!

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"

Re: Testing official self-extract makeself .run fails to extract / anyone could test it?

[Nuno Teixeira]

Thank you for testing.

I will do further tests with older releases too and hope that upstream
fixes it.

Thanks

DutchDaemon - FreeBSD Forums Administrator 
escreveu no dia sexta, 15/01/2021 à(s) 11:52:

> On 15/01/2021 12:38, Nuno Teixeira wrote:
> > Hello,
> >
> > I need that someone test official archivers/makeself self-extratable bin
> to
> > see if error is the same:
> >
> > https://github.com/megastep/makeself/issues/238
> >
> > Download link:
> >
> https://github.com/megastep/makeself/releases/download/release-2.4.2/makeself-2.4.2.run
> >
> > Run: sh makeself-2.4.2.run
> >
> > Thanks,
> >
> > Nuno Teixeira
>
> # ./makeself-2.4.2.run
> Creating directory makeself-2.4.2
> Verifying archive integrity...  100%   MD5 checksums are OK. All good.
> Uncompressing Makeself v2.4.2  100%   ... Extraction failed.
> Terminated
>
> --
>
> # sh -x makeself-2.4.2.run
> + umask
> + ORIG_UMASK=0022
> + test n '=' n
> + umask 077
> + CRCsum=3945225848
> + MD5=6ec4e617e8ed15e4612e05e0a8ad18cd
> + SHA=
> + TMPROOT=/tmp
> + USER_PWD=/tmp/test
> + export USER_PWD
> + ARCHIVE_DIR=.
> + export ARCHIVE_DIR
> + label='Makeself v2.4.2'
> + script=echo
> + scriptargs='Makeself has extracted itself'
> + cleanup_script=''
> + licensetxt=''
> + helpheader=''
> + targetdir=makeself-2.4.2
> + filesizes=31397
> + keep=y
> + nooverwrite=n
> + quiet=n
> + accept=n
> + nodiskspace=n
> + export_conf=n
> + decrypt_cmd=''
> + skip=668
> + print_cmd_arg=''
> + type printf
> + print_cmd=printf
> + test -d /usr/xpg4/bin
> + test -d /usr/sfw/bin
> + unset CDPATH
> + finish=true
> + xterm_loop=''
> + noprogress=n
> + nox11=n
> + copy=none
> + ownership=n
> + verbose=n
> + cleanup=y
> + cleanupargs=''
> + initargs=''
> + true
> + break
> + test xn '=' xy -a xn '=' xy
> + id -u
> + test xn '=' xy -a 0 -ne 0
> + test xnone '!=' xphase2
> + MS_PrintLicense
> + test x '!=' x
> + test xn '=' xn
> + tty -s
> + :
> + test xmakeself-2.4.2 '=' x.
> + test xy '=' xy
> + test xn '=' xy
> + test xn '=' xn
> + echo 'Creating directory makeself-2.4.2'
> Creating directory makeself-2.4.2
> + tmpdir=makeself-2.4.2
> + dashp=-p
> + mkdir -p makeself-2.4.2
> + pwd
> + location=/tmp/test
> + test x '!=' x1
> + MS_Check makeself-2.4.2.run
> +
>
> OLD_PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin:
> +
>
> PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin::/bin:/usr/bin:/sbin:/usr/local/ssl/bin:/usr/local/bin:/opt/openssl/bin
> + MD5_ARG=''
> + exec
> + MD5_PATH=''
> + test -x ''
> + exec
> + MD5_PATH=/sbin/md5
> + test -x /sbin/md5
> +
>
> PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin:
> + exec
> + SHA_PATH=/usr/local/bin/shasum
> + test -x /usr/local/bin/shasum
> + test xn '=' xn
> + MS_Printf 'Verifying archive integrity...'
> + printf 'Verifying archive integrity...'
> Verifying archive integrity...+ head -n 668 makeself-2.4.2.run
> + wc -c
> + tr -d ' '
> + offset=16914
> + verb=''
> + i=1
> + echo 3945225848
> + cut '-d ' -f1
> + crc=3945225848
> + test -x /usr/local/bin/shasum
> + basename /usr/local/bin/shasum
> + test xshasum '=' xshasum
> + SHA_ARG='-a 256'
> + echo 
> + cut '-d ' -f1
> + sha=
> + test x
> '=' x
> + test x '=' xy
> + test -x /sbin/md5
> + basename /sbin/md5
> + test xmd5 '=' xdigest
> + echo 6ec4e617e8ed15e4612e05e0a8ad18cd
> + cut '-d ' -f1
> + md5=6ec4e617e8ed15e4612e05e0a8ad18cd
> + test x6ec4e617e8ed15e4612e05e0a8ad18cd '='
> x00

Testing official self-extract makeself .run fails to extract / anyone could test it?

[Nuno Teixeira]

Hello,

I need that someone test official archivers/makeself self-extratable bin to
see if error is the same:

https://github.com/megastep/makeself/issues/238

Download link:
https://github.com/megastep/makeself/releases/download/release-2.4.2/makeself-2.4.2.run

Run: sh makeself-2.4.2.run

Thanks,

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"

can't build poudriere i386 arch: net/gitup

[Nuno Teixeira]

Hello,

I'm trying to test a port in a different arch:
doas poudriere bulk -j 114i386 -p ports net/gitup
 awk: can't open file
/usr/local/poudriere/jails/114i386/usr/include/sys/param.h

Could anyone please try latest gitup commit for me?
https://github.com/johnmehr/gitup/issues/30
___
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: gmake can't find GNUmakefile, only Makefile?

[Nuno Teixeira]

Thanks!

It works perfectly!

Fernando Apesteguía  escreveu no dia
segunda, 4/01/2021 à(s) 12:49:

>
>
> On Mon, Jan 4, 2021 at 1:45 PM Nuno Teixeira  wrote:
>
>> Hello,
>>
>> I'm porting a c'++ program that  depends on gmake.
>>
>> upstream uses GNUmakefile instead of Makefile name.
>>
>
> Try:
>
> MAKEFILE=  GNUmakefile
>
>
>> Thats strange that gmake sees GNUmakefile when doing gmake in work/port
>> but
>> port itself fails with:
>>
>> ---
>> gmake[2]: Entering directory
>> '/usr/home/nunotex/Work/ports/cxxmatrix/work/port'
>> gmake[2]: Makefile: No such file or directory
>> gmake[2]: *** No rule to make target 'Makefile'.  Stop.
>> gmake[2]: Leaving directory
>> '/usr/home/nunotex/Work/ports/cxxmatrix/work/port'
>> ===> Compilation failed unexpectedly.
>> ---
>>
>> How do I tell gmake to find it?,
>>
>> Thanks,
>>
>> 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"
>>
>
___
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"

gmake can't find GNUmakefile, only Makefile?

[Nuno Teixeira]

Hello,

I'm porting a c'++ program that  depends on gmake.

upstream uses GNUmakefile instead of Makefile name.
Thats strange that gmake sees GNUmakefile when doing gmake in work/port but
port itself fails with:

---
gmake[2]: Entering directory
'/usr/home/nunotex/Work/ports/cxxmatrix/work/port'
gmake[2]: Makefile: No such file or directory
gmake[2]: *** No rule to make target 'Makefile'.  Stop.
gmake[2]: Leaving directory
'/usr/home/nunotex/Work/ports/cxxmatrix/work/port'
===> Compilation failed unexpectedly.
---

How do I tell gmake to find it?,

Thanks,

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"

Re: Correct syntax for CFLAGS to change a -DCONFIG_FILE_PATH=...

[Nuno Teixeira]

 Thanks!

Nuno

Renato Botelho  escreveu no dia quarta, 30/12/2020 à(s)
12:14:

> On 30/12/20 05:31, Nuno Teixeira wrote:
> > Hello,
> >
> > Recently upstream changed is example.c to have:
> >
> > #ifndef CONFIG_FILE_PATH
> > #define CONFIG_FILE_PATH "./example.conf"
> > #endif
> >
> > I found a way to change it in example port Makefile:
> >
> > CFLAGS+= -https://github.com/johnmehr/gitup/pull/17=\\\
> "${LOCALBASE}/etc/example.conf\\\"
> >
> > It works fine.
> >
> > Am I doing the correct way and correct syntax? Those "\\\" ... "\\\" make
> > me some confusion.
>
> I've opened a PR [1] to improve gitup's Makefile and after it's accepted
> you will be able to use:
>
> MAKE_ENV+= CONFIG_FILE_PATH=${LOCALBASE}/etc/gitup.conf
>
> [1] https://github.com/johnmehr/gitup/pull/17
>
> --
> Renato Botelho
>
___
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"

Correct syntax for CFLAGS to change a -DCONFIG_FILE_PATH=...

[Nuno Teixeira]

Hello,

Recently upstream changed is example.c to have:

#ifndef CONFIG_FILE_PATH
#define CONFIG_FILE_PATH "./example.conf"
#endif

I found a way to change it in example port Makefile:

CFLAGS+= -DCONFIG_FILE_PATH=\\\"${LOCALBASE}/etc/example.conf\\\"

It works fine.

Am I doing the correct way and correct syntax? Those "\\\" ... "\\\" make
me some confusion.

Thanks,

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"

Re: How to fix/patch hardcoded values

[Nuno Teixeira]

Hello!,

man(1) gitup only references:
Files:
${PREFIX}/etc/gitup.conf  Default location of the gitup configuration file.

But yes, thats makes sense a per-user .config file, maybe in ~ or in
~/.config folder.

Thanks!

Chris  escreveu no dia terça, 29/12/2020 à(s)
08:23:

> On 2020-12-29 00:07, Mathieu Arnold wrote:
> > On Sun, Dec 27, 2020 at 09:58:13PM +0000, Nuno Teixeira wrote:
> >> Hello I've just submited a new port net/gitup
> >> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252220> and I used a
> >> simple workaround to help program find its config in /usr/local/etc
> instead
> >> of (hardcoded) ./
> >>
> >> --- gitup.c.orig 2020-12-27 21:16:22 UTC
> >> +++ gitup.c
> >> @@ -2030,7 +2030,7 @@ main(int argc, char **argv)
> >> ...
> >> - const char *configuration_file = "./gitup.conf";
> >> + const char *configuration_file = "/usr/local/etc/gitup.conf";
> >>
> >> Now I'm thinking that this might not be the best fix in case PREFIX is a
> >> different one.
> >>
> >> Could I have an opinion on this?
> >
> > You need to change the patch to use %%PREFIX%% or %%LOCALBASE%%
> > depending on whether this is a reference to a path/file installed by the
> > software or by one of its dependency.  Then, in a post-patch target, you
> > need to use REINPLACE_CMD to replace those to by they variables
> > equivalent, something like:
> >
> > post-patch:
> >   ${REINPLACE_CMD} -e 's,%%PREFIX%%,${PREFIX}' ${WRKSRC}/githup.c
> It seems to me that you might also want to allow the user to reference
> a/their config from within their home dir (~/). But of course that's
> purely optional. Just thought I might mention it in case it mattered.
> ___
> 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: How to fix/patch hardcoded values

[Nuno Teixeira]

Hello,

I'm using:
${REINPLACE_CMD} 's,\./gitup.conf,${PREFIX}/etc/gitup.conf,'
${WRKSRC}/gitup.c

I didn't know about that sintax with "%":
${REINPLACE_CMD} -e 's,%%PREFIX%%,${PREFIX}' ${WRKSRC}/githup.c

Does it make any difference between the two expressions?

Thanks

Mathieu Arnold  escreveu no dia terça, 29/12/2020 à(s)
08:07:

> On Sun, Dec 27, 2020 at 09:58:13PM +, Nuno Teixeira wrote:
> > Hello I've just submited a new port net/gitup
> > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252220> and I used a
> > simple workaround to help program find its config in /usr/local/etc
> instead
> > of (hardcoded) ./
> >
> > --- gitup.c.orig 2020-12-27 21:16:22 UTC
> > +++ gitup.c
> > @@ -2030,7 +2030,7 @@ main(int argc, char **argv)
> > ...
> > - const char *configuration_file = "./gitup.conf";
> > + const char *configuration_file = "/usr/local/etc/gitup.conf";
> >
> > Now I'm thinking that this might not be the best fix in case PREFIX is a
> > different one.
> >
> > Could I have an opinion on this?
>
> You need to change the patch to use %%PREFIX%% or %%LOCALBASE%%
> depending on whether this is a reference to a path/file installed by the
> software or by one of its dependency.  Then, in a post-patch target, you
> need to use REINPLACE_CMD to replace those to by they variables
> equivalent, something like:
>
> post-patch:
> ${REINPLACE_CMD} -e 's,%%PREFIX%%,${PREFIX}' ${WRKSRC}/githup.c
>
> --
> Mathieu Arnold
>
___
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"

Don't like git? gitup is here for you

[Nuno Teixeira]

I'm proud to announce that net/gitup is almost landing. 252220
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252220>

Thanks all,
Thanks Kimura. It's so good to learn! 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"

How to fix/patch hardcoded values

[Nuno Teixeira]

Hello I've just submited a new port net/gitup
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252220> and I used a
simple workaround to help program find its config in /usr/local/etc instead
of (hardcoded) ./

--- gitup.c.orig 2020-12-27 21:16:22 UTC
+++ gitup.c
@@ -2030,7 +2030,7 @@ main(int argc, char **argv)
...
- const char *configuration_file = "./gitup.conf";
+ const char *configuration_file = "/usr/local/etc/gitup.conf";

Now I'm thinking that this might not be the best fix in case PREFIX is a
different one.

Could I have an opinion on this?

Thanks,

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"

Need a commiter

[Nuno Teixeira]

Hello,

Could a commiter take a look at PR251982
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251982> ?

Thanks,

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"

Fwd: [diasurgical/devilutionX] Update CMakeLists.txt: FreeBSD specific POSIX extensions (#940)

[Nuno Teixeira]

-- Forwarded message -
De: Anders Jenbo 
Date: terça, 8/12/2020 à(s) 10:41
Subject: Re: [diasurgical/devilutionX] Update CMakeLists.txt: FreeBSD
specific POSIX extensions (#940)
To: diasurgical/devilutionX 
Cc: nunotexbsd , Author 


Merged #940 <https://github.com/diasurgical/devilutionX/pull/940> into
master

Thanks Malavon who made this possible.
Thanks FreeBSD.

Nuno Teixeira

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/diasurgical/devilutionX/pull/940#event-4084113859>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKNR7XH3NUBIZU3H2ZLSZSDSTX7GVANCNFSM4URUIQEQ>
.
___
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: textproc/cast2gif not compiling on i386

[Nuno Teixeira]

Ok, thanks!

Rainer Hurling  escreveu no dia segunda, 7/12/2020 à(s)
17:53:

> Hi Nuno,
>
> I think you are right. cargo-crates/font-kit lists only the following
> platforms:
>
>   x86_64-unknow-linux-gnu
>   x86_64-pc-windows-msvc
>   i686-pc-windows-msvc
>   x86_64-apple-darwin
>
> ONLY_FOR_ARCHS=amd64 seems right to me.
>
> Greetings,
> Rainer
>
>
> Am 07.12.20 um 08:09 schrieb Nuno Teixeira:
> > Hello,
> >
> > textproc/cast2gif is not compiling on i386 and "expected `i32`, found
> > `i64`" error seems to tell that font-kit rust dependency is not i386
> > buildable.
> >
> > Should I use ONLY_FOR_ARCHS= amd64?
> >
> > Full log
> > <
> http://beefy10.nyi.freebsd.org/data/114i386-default/557100/logs/cast2gif-0.1.0.p1.log
> >
> >
> > Thanks,
> >
> > Nuno Teixeira
> >
> > (...)
> >
> > error[E0308]: mismatched types
> >-->
> /wrkdirs/usr/ports/textproc/cast2gif/work/cast2gif-4f76eeb/cargo-crates/font-kit-0.6.0/src/loaders/
> freetype.rs:811:21
> > |
> > 811 | yy: matrix.w() as i64,
> > | ^ expected `i32`, found `i64`
> >
> > error: aborting due to 6 previous errors
> >
> > For more information about this error, try `rustc --explain E0308`.
> > error: could not compile `font-kit`
> >
> > Caused by:
> >   process didn't exit successfully: `/usr/local/bin/rustc --crate-name
> > font_kit --edition=2018
> >
> /wrkdirs/usr/ports/textproc/cast2gif/work/cast2gif-4f76eeb/cargo-crates/font-kit-0.6.0/src/
> lib.rs
> > --error-format=json --json=diagnostic-rendered-ansi,artifacts
> > --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C
> > linker-plugin-lto --cfg 'feature="default"' --cfg 'feature="freetype"'
> > --cfg 'feature="loader-freetyp
> >
> > (...)
> > ___
> > 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: textproc/cast2gif not compiling on i386

[Nuno Teixeira]

https://docs.rs/crate/font-kit/0.10.0 only show builds for x86-64 and i686

Nuno Teixeira  escreveu no dia segunda, 7/12/2020
à(s) 07:09:

> Hello,
>
> textproc/cast2gif is not compiling on i386 and "expected `i32`, found
> `i64`" error seems to tell that font-kit rust dependency is not i386
> buildable.
>
> Should I use ONLY_FOR_ARCHS= amd64?
>
> Full log
> <http://beefy10.nyi.freebsd.org/data/114i386-default/557100/logs/cast2gif-0.1.0.p1.log>
>
> Thanks,
>
> Nuno Teixeira
>
> (...)
>
> error[E0308]: mismatched types
>--> 
> /wrkdirs/usr/ports/textproc/cast2gif/work/cast2gif-4f76eeb/cargo-crates/font-kit-0.6.0/src/loaders/freetype.rs:811:21
> |
> 811 | yy: matrix.w() as i64,
> | ^ expected `i32`, found `i64`
>
> error: aborting due to 6 previous errors
>
> For more information about this error, try `rustc --explain E0308`.
> error: could not compile `font-kit`
>
> Caused by:
>   process didn't exit successfully: `/usr/local/bin/rustc --crate-name 
> font_kit --edition=2018 
> /wrkdirs/usr/ports/textproc/cast2gif/work/cast2gif-4f76eeb/cargo-crates/font-kit-0.6.0/src/lib.rs
>  --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type 
> lib --emit=dep-info,metadata,link -C opt-level=3 -C linker-plugin-lto --cfg 
> 'feature="default"' --cfg 'feature="freetype"' --cfg 'feature="loader-freetyp
>
> (...)
>
>
___
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"

textproc/cast2gif not compiling on i386

[Nuno Teixeira]

Hello,

textproc/cast2gif is not compiling on i386 and "expected `i32`, found
`i64`" error seems to tell that font-kit rust dependency is not i386
buildable.

Should I use ONLY_FOR_ARCHS= amd64?

Full log
<http://beefy10.nyi.freebsd.org/data/114i386-default/557100/logs/cast2gif-0.1.0.p1.log>

Thanks,

Nuno Teixeira

(...)

error[E0308]: mismatched types
   --> 
/wrkdirs/usr/ports/textproc/cast2gif/work/cast2gif-4f76eeb/cargo-crates/font-kit-0.6.0/src/loaders/freetype.rs:811:21
|
811 | yy: matrix.w() as i64,
| ^ expected `i32`, found `i64`

error: aborting due to 6 previous errors

For more information about this error, try `rustc --explain E0308`.
error: could not compile `font-kit`

Caused by:
  process didn't exit successfully: `/usr/local/bin/rustc --crate-name
font_kit --edition=2018
/wrkdirs/usr/ports/textproc/cast2gif/work/cast2gif-4f76eeb/cargo-crates/font-kit-0.6.0/src/lib.rs
--error-format=json --json=diagnostic-rendered-ansi,artifacts
--crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C
linker-plugin-lto --cfg 'feature="default"' --cfg 'feature="freetype"'
--cfg 'feature="loader-freetyp

(...)
___
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: Could a comitter take a look

[Nuno Teixeira]

Rainer Hurling  escreveu no dia sábado, 28/11/2020 à(s)
09:14:

>
> For PR 251064 (textproc/cast2gif) I showed in comment #7, that there is
> a problem building your port. This has to be solved by someone (probably
> you?) before a commit.
>

I can't test why is this rust port failing compile on 11.4 because my
current laptop does't have enough ram, but soon I will have a better one to
test with poudriere.
Any hint on why a rust port is building ok on 12.2 but not on 11.4?


> > - adoption/takeover: 251072
> >  251397
> > 
>

251397  is ready
for takeover maintainership.

Thanks

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

Could a comitter take a look

[Nuno Teixeira]

Hello,

Could a commiter take a look at:

- new ports: 251064
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251064> 251309
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251309>

- adoption/takeover: 251072
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251072> 251397
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251397>

Thanks,

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"

rust apps failing compiling on 11.4 but ok on 12.2?

[Nuno Teixeira]

Hello,

Does anyone seing rust apps compiling ok on FreeBSD 12.2 but not on 11.4?

Theres a strange compile error on 11.4 about a new app: Bug 251064
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251064>

What should I do to debug and find a fix for it?

I'm using 12.2 on a very old laptop with only 1GB RAM (until PC is
repaired) and I can't use poudriere because it can't compile rust on 11.4.

Maybe use a 11.4 jail and use rust package to build that port failing.

Thanks,

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"

[NEW PORT] textproc/cast2gif

[Nuno Teixeira]

Hello to all,

Could a commiter take a look at Bug 251064
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251064> ?

Thanks,

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"

[NEW PORT] textproc/cast2gif: Tool to render Asciinema cast files to GIFs

[Nuno Teixeira]

Hello to all,

A tool to render textproc/py-asciinema cast files to GIF.
This is a pre-release.
Please test it and use https://github.com/katharostech/cast2gif/issues if
necessary.
Bug 251064 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251064>

Thanks,

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"

Re: Correct path for man pages

[Nuno Teixeira]

Got it, thanks!

Mateusz Piotrowski <0...@freebsd.org> escreveu no dia domingo, 1/11/2020
à(s) 18:20:

> On 11/1/20 2:41 PM, Nuno Teixeira wrote:
> > I remember reading something about correct path for man pages:
> >
> > ${STAGEDIR}${PREFIX}/share/man/manN
> > or
> > ${STAGEDIR}${MAN1PREFIX}/man/manN
> >
> > Can't find original post about it.
>
> Probably the CHANGES file in the ports tree:
>
> 20200115:
> AUTHOR: b...@freebsd.org
>
>${PREFIX}/share/man is now a valid location for manpages ${PREFIX}/man
> being
>considered as deprecated.
>
> Cheers,
>
> Mateusz
>
>
___
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"

Correct path for man pages

[Nuno Teixeira]

Hello,

I remember reading something about correct path for man pages:

${STAGEDIR}${PREFIX}/share/man/manN
or
${STAGEDIR}${MAN1PREFIX}/man/manN

Can't find original post about it.

Thanks,

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"

New port: Fast, funny, everyone wanted? new cowsay!!

[Nuno Teixeira]

Hello,

New port: games/neo-cowsay written in Go.

Just try "--super" option, it's awesome!

Take a look at 250771
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250771>

Thanks,

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"

games/OpenDiablo2 update to 0.1 pre-alpha release!

[Nuno Teixeira]

Hello,

OpenDiablo2 <https://github.com/OpenDiablo2/OpenDiablo2> released is first
pre-alpha release!

PR 250666 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250666> ready!

Thanks,

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"

archivers/makeself adopted/updated!

[Nuno Teixeira]

Hello,

A very nice program that was not updated for years.

Please take a look at 250577
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250577>

Thanks,

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"

Could a comitter take a look at new port?

[Nuno Teixeira]

Hello,

I will be very pleased if a commiter could take a look at 250426
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=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"

Need a comitter at PR 247496 (security/doas)

[Nuno Teixeira]

Hello,

Could a comitter take a look at PR 247496
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247496> please.

Thanks,

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"

games/devilutionx update: please commit

[Nuno Teixeira]

Hello,

Could a commiter please look at 244722
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244722>
(games/devilutionx update) and 244399
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244399> (games/cursive
adoption)?

Thanks,

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"

Could a comitter take a look at my PRs?

[Nuno Teixeira]

Hello,

Could a comitter take a look at my PRs:

graphics/viewnior: update to 1.7
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243529>
graphics/viewnior: take maintainership
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243726>
editors/xi-core: update to 0.3.0 rel
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243799>
misc/cmatrix: Adopt/Update to 2.0
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243915>

Thanks,

Nuno Teixeira


<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243915>
___
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"

x11-wm/aphelia: update timeout from 2019-11-15

[Nuno Teixeira]

Hello,

Please update x11-wm/aphelia to g20190913, PR 241990
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241990>

I can take maintanership of this port.

Thanks,

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"