ports: 11.2 install incompatible with portsnap?

[Gary Aitken]

On 11/15/18 13:38, RW via freebsd-questions wrote:
> On Thu, 15 Nov 2018 10:18:14 -0700
> Gary Aitken wrote:
> 
> 
>> root at breakaway:/usr/ports # portsnap update
>> /usr/ports was not created by portsnap.
>> You must run 'portsnap extract' before running 'portsnap update'.
>>
>> Note the next-to-last line:
>>     /usr/ports was not created by portsnap.
>>
>> That may be true.  It was created during a sysinstall, but
>> I don't know what the mechanism used to create it was.
>>
> 
> As a general rule update tools should be allowed to start
> with a clean directory unless you know for a fact that adopting a
> exiting tree is harmless.
> 
> portsnap keeps a hidden file in the ports directory that records what
> it installed in that instance of the port tree - it need to be
> there to perform an update.

So what's the point of installing the ports tree during a sysinstall
if it has to be re-extracted on the first update after the install?
Why not recommend not installing it during sys install and doing a
fetch + extract first thing after installation?  It just wastes time
and resources doing the task twice.

>> Is this now normal?
> 
> I think it always was.

I don't recall having this issue on 10.x (not sure which) or 8.x.
I'm not absolutely certain I installed ports as part of the sys install,
but I'm pretty sure I did on at least one of them.

Gary