Fix typo Big Sur 1.x -> Big Sur 11.x
> On Feb 28, 2021, at 7:10 PM, Peter Teeson <peter.tee...@me.com> wrote:
>
> Hi Jürgen:
>
> Thanks for setting up git.
>
> I have confirmed that macOS Mojave 10.14 does have both svn and git installed
> in /usr/bin.
>
> However macOS Catalina 10.15 does not have svn
> <https://developer.apple.com/documentation/macos-release-notes/macos-catalina-10_15-release-notes
>
> <https://developer.apple.com/documentation/macos-release-notes/macos-catalina-10_15-release-notes>>
> "Command line tool support for Subversion — including svn, git-svn, and
> related commands — is no longer provided by Xcode. (50266910)”
>
> So macOS' current release, Big Sur 1.x also does not have it.
>
> Apparently there is 3rd party support for installing svn via Homebrew.
>
> respect…
>
> Peter
>> On Feb 28, 2021, at 2:21 PM, Dr. Jürgen Sauermann
>> <m...@xn--jrgen-sauermann-zvb.de <http://jrgen-sauermann-zvb.de/>> wrote:
>>
>> Hi again, Peter,
>>
>> I believe I managed to set up git for the GNU APL repository at savannah.
>> That should hopefully remove the need to install SVN for Apple users (even
>> though they might be better off installing it).
>>
>> Best Regards,
>> Jürgen
>>
>>
>> On 2/28/21 11:49 AM, Dr. Jürgen Sauermann wrote:
>>> Hi Peter,
>>>
>>> see below.
>>>
>>> Best Regards,
>>> Jürgen
>>>
>>> On 2/28/21 12:10 AM, Peter Teeson wrote:
>>>> 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.tee...@me.com
>>>>> <mailto:peter.tee...@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-jo...@usa.net <mailto:edxmail-jo...@usa.net>.
>>>>> In this revision I plan to not recommend the tarball.
>>>>>
>>> That's fine. The GNU tarball has little value, but as I understand it it is
>>> the standard way
>>> of delivering a GNU project. Many GNU/Linux distributions (including
>>> Debian) fetch the
>>> latest tar ball (and not the latest SVN checkout) as part of their build
>>> process. For that
>>> reason the tarball should remain, even though it is less useful for an
>>> individual user.
>>>>> (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.
>>>>>
>>> Actually savannah (where the GNU APL repository resides) supports both SVN
>>> and Git
>>> checkouts. Its only that I have to find out how to configure that on
>>> savannah (and maybe
>>> update the GNU APL home page). Let me look into this.
>>>>> 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?
>>>>>
>>> I should mention that the savannah repo, be it accessed Git or SVN, is
>>> always updated from the tarball
>>> (see Makefile.am and Makefile.include) and not directly from SVN like this:
>>>
>>> Jürgen's SVN → tarball → tar -xvf → checked-out savannah SVN → svn commit
>>> to savannah
>>>
>>> by the make target "EXPO". That chain would be broken when the tarball is
>>> removed completely.
>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
