Date: Thu, 15 Nov 2018 20:38:53 +0000 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: ports: 11.2 install incompatible with portsnap? Message-ID: <20181115203853.74f6d6d5@gumby.homeunix.com> In-Reply-To: <0b12bf4c-8a2a-9642-7e72-600b6798543d@dreamchaser.org> References: <0b12bf4c-8a2a-9642-7e72-600b6798543d@dreamchaser.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 15 Nov 2018 10:18:14 -0700 Gary Aitken wrote: > root@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. > Is this now normal? I think it always was.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181115203853.74f6d6d5>