Re: Porting forks

From: Nuno Teixeira <>
Date: Fri, 24 Feb 2023 15:25:46 UTC
I installed fork version but it seg fault exacly the same as
abuse 0.8
Abuse version 0.8
Sound: Enabled
Specs : main file set to abuse.spe
Protocol Installed : UNIX generic TCPIP
Lisp: 527 symbols defined, 99 system functions, 319 pre-compiled functions
(load "abuse.lsp") [..                                      ]Segmentation
fault (core dumped)
Also that might be some problem with this port because there is no amd64
packages available but it build ok in current.

I will continue digging and open a PR with port fork diff, so more people
test it (I hope)

Related to portname, I will choose abuse-xenoveritas (PKGNAMESUFFIX=
-xenoveritas) because this fork don't include some files because of
licenses issues.


Tatsuki Makino <> escreveu no dia quinta,
23/02/2023 à(s) 22:17:

> Hello.
> I'm a little concerned about it too, but...
> > xenoveritas-abuse
> > abuse-xenoveritas
> I think it would be that way, and I don't think it would be that way :)
> I already have a synthesizer helm port in my local tree.
> However, it's name conflicts with sysutils/helm.
> So I work around it by doing the following:
> PORTNAME=       helm
> PKGNAMESUFFIX=  -synthesizer
> The portname should match the name in the distfile, so a different name
> will increase the number of somewhat cumbersome variable definitions.
> For example, audio/libamrnb, audio/libamrwb and astro/geographiclib.
> Since PKGNAME{PREFIX,SUFFIX} is also used to indicate differences in
> flavor, the above method raises the possibility of making that distinction
> difficult.
> What is the best way to do it?
> Regards.

Nuno Teixeira
FreeBSD Committer (ports)