Date: Tue, 14 Nov 2017 12:29:55 -0500 From: Baho Utot <baho-utot@columbus.rr.com> To: freebsd-questions@freebsd.org Subject: Re: Updating Instructions Message-ID: <81090cac-6f93-7262-4986-44e7512492cf@columbus.rr.com> In-Reply-To: <20171114154413.GA57677@gmail.com> References: <BN6PR2001MB1730B1AE0B338F8A0EB1F48A80280@BN6PR2001MB1730.namprd20.prod.outlook.com> <20171114132056.2e1122f8@gumby.homeunix.com> <BN6PR2001MB1730EA51F47D66D0DC05311580280@BN6PR2001MB1730.namprd20.prod.outlook.com> <20171114154413.GA57677@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/14/2017 10:44 AM, Matt Smith wrote: > On Nov 14 15:40, Carmel NY wrote: >> On Tue, 14 Nov 2017 13:20:56 +0000, RW via freebsd-questions stated: >> >>> Have you any particular reason to think they are needed? There are no >>> such instructions for updating with pkg and that's what synth uses >>> after building local packages. >> >> Actually, from time to time there are: >> >> (1) 20171107 >> (2) 20171006 >> (3) 20170808 >> (4) 20170807 >> (5) 20170721 >> >> Those are just a few. I agree that it is not as well documented as >> "portmaster" or "portupgrade" though. >> > > This is most likely because pkg, poudriere, and synth are all "clean > room build/install" tools and should just do the correct thing by > default without any intervention required. Whereas portmaster and > portupgrade don't run inside any chroot or jail environments and are > directly affected by things being found in the build host. > > A lot of the time this requires manual intervention, uninstalling > things, moving things out the way etc. before you can do an upgrade. > > You just simply don't need to do that with the clean-room tools. > Unless the base system has a negative influance upon the port in question
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?81090cac-6f93-7262-4986-44e7512492cf>