Re: To tarball or not to tarball? P.S.

[Peter Teeson]

P.S. Apple no longer distributes svn (as per johnh experience). But instead git is installed. 

I will check in a few days when I boot into my clean Mojave if it’s part of the macOS install.

Or whether it comes by installing Xcode and/or Command line Tools. 

Will post here when I have proof.

respect

Peter

On Feb 27, 2021, at 3:30 PM, Peter Teeson <peter.teeson@me.com> wrote:

Hi Jürgen:

The GNU APL page mentions downloading the tarball as the normal way to proceed.

I’m revising "GNU APL on Mac" pdf as a result of feedback from edxmail-johnh@usa.net.

In this revision I plan to not recommend the tarball.

(1) How do you feel about dropping the tarball altogether?

 If you don’t want to do that I would ask for a section for GNU APL on Macintosh.

I could provide brief download wording for git.  The git function “gitsvn" makes thing easy.

That way they would not have to download the whole package to get the Mac pdf

Apple has long ago moved from cvs -> svn -> git as their default source control in Xcode.

Terminal waltz would still remain as the default build song.

(2) Incidentally this brings up the question of why bother with a release tarball anyway?

It’s a lot of work, as you once mentioned. As of today it is 17 months out of date.

And has resulted in a number of threads related specifically to it. 

Which were resolved by using the latest svn.

My sense is that the people who do want to try GNU APL are probably developers.

So they should be comfortable with the Terminal/Command Line approach.

(3) So how do you feel about dropping the tarball altogether and adjusting the GNU APL page accordingly?

with respect….

Peter