[PATCH] user: Add hints for macOS Catalina

[Chris Johns]

On 8/11/19 7:08 pm, Sebastian Huber wrote:
> On 08/11/2019 08:50, Chris Johns wrote:
>>
>>> On 8 Nov 2019, at 5:20 pm, Sebastian Huber
>>> <Sebastian.Huber at embedded-brains.de> wrote:
>>>
>>> On 07/11/2019 22:04, Chris Johns wrote:
>>>>> On 7/11/19 7:51 pm, Sebastian Huber wrote:
>>>>> Use macOS throughout.  Order release hints so that the latest macOS
>>>>> release comes first.
>>>> Thanks for this.
>>>>> +Catalina
>>>>> +~~~~~~~~
>>>>> +
>>>>> +In the
>>>>> +`macOS Catalina 10.15 Release Notes
>>>>> <https://developer.apple.com/documentation/macos_release_notes/macos_catalina_10_15_release_notes>`_
>>>>>
>>>>> +Apple deprecated several scripting language runtimes such as Python 2.7.
>>>> This is almost right, it is present in Catalina but will be removed in future
>>>> versions. This is inline with the removal of tools like emacs and so expected.
>>>
>>> I used more or less the Apple wording. Deprecated means to me that you should
>>> start to investigate alternatives.
>>
>>   Sure.
> 
> Ok, good. Do I have to change anything in the patch?

It would be nice to be as clear as possible. Would adding something about being
deprecated means we suggest you use python3 from ... ?

>>
>>> So, I added the recommendation to install Python from python.org. Apple says:
>>>
>>> "Use of Python 2.7 isn’t recommended as this version is included in macOS for
>>> compatibility with legacy software. Future versions of macOS won’t include
>>> Python 2.7. Instead, it’s recommended that you run python3 from within
>>> Terminal. (51097165)"
>>>
>>> What would you recommend to RTEMS users?
>>
>> I think we should say they use python 3 and python.org. I will have to update
>> my build box.
>>
>> We will support python 2 for a while to come as there will be a number of
>> older hosts in production.
> 
> Yes, for the build system Python 2.7 support is on my list.

I suppose this means we need to regression test against both versions on
platforms with both versions? I wonder if waf supports a dry-run type option so
we can test the build system without needing to run a build?

Chris