Re: Toward a MacPorts port that tracks 0.7.9

> On Feb 3, 2025, at 4:10 AM, Marvin Littlewood =
<[email protected]> wrote:
>=20
> I recognise that there are flatpak and snap distributions for Fedora, =
Ubuntu and homebrew for the Mac, so I wondered what it would take to =
create a portfile. Crucial to that idea is being able to build the =
latest tarball, so I recorded my experiences.
>=20
> Is everyone happy for me to continue on this path for the moment? (I =
have a lot to learn about how MacPorts works and whether building on a =
client machine is a viable approach, so I am uncertain as how this idea =
will turn out.)

Hi:

Are you saying that you want to be able to build development versions of =
gforth on your Mac so you can identify bugs and help the developers?  If =
so, MacPorts isn=E2=80=99t particularly suited for such work.  MacPorts =
is designed to distribute stable, tested, released software. =20

So doing the builds outside of MacPorts is going to be your best choice. =
 Likely by cloning the git repo and doing a git pull prior to building.  =
Of course, you can use the libraries installed via MacPorts.  That=E2=80=99=
s just libffi and libtool, right?  Or has something changed?

BTW, your earlier email mentioned a segmentation fault while building =
gforth.  In MacPorts, we disabled parallel builds for gforth=E2=80=94it =
was a very long time ago but I think this was the symptom.  You might =
try issuing the make command with "-j 1=E2=80=9D.  Since gforth isn=E2=80=99=
t a long build, this isn=E2=80=99t too much of a hardship. =20

Whenever a new stable version of gforth is released, it should be pretty =
trivial to update MacPorts.  Even if I=E2=80=99m not involved, you just =
need to file a bug in the MacPorts Trac system and one of the =
maintainers will eventually deal with it.  Even better is to submit a =
pull request to MacPorts on GitHub.  They tend to be dealt with very =
quickly. =20

HTH,

Craig