Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Apr 2016 10:06:40 -0600 (MDT)
From:      Warren Block <wblock@wonkity.com>
To:        Polytropon <freebsd@edvax.de>
Cc:        JosC <bsduser@cloudzeeland.nl>, FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: Ports upgrade script
Message-ID:  <alpine.BSF.2.20.1604161004330.46192@wonkity.com>
In-Reply-To: <20160416172045.8010cc7b.freebsd@edvax.de>
References:  <2daca22c-7719-0776-fbe8-3c37021298bf@cloudzeeland.nl> <CAA2O=b9kHNz-q8NP_txAveRRw57jLWg8yMnTZvcQm0F4M98hOA@mail.gmail.com> <2e223983-d2ff-fd97-caba-732fd92aa20b@cloudzeeland.nl> <20160416172045.8010cc7b.freebsd@edvax.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Sat, 16 Apr 2016, Polytropon wrote:

> On Sat, 16 Apr 2016 16:34:16 +0200, JosC wrote:
>>
>> In een bericht van 16-4-2016 12:18:
>>>
>>> Portsnap isn't compatible with svn.
>>>
>> So I think I should revise the way I update my ports.
>> What I did with my 9.3 BSD was the following script (which worked
>> perfectly):
>>
>> !/bin/sh
>> cd /local/user/etc
>> svn update /usr/src
>> svn update /usr/ports
>> #
>> cd /usr/ports
>> make fetchindex
>> portsdb -fu
>> #
>> #
>> cd /usr/local/etc
>> portupgrade -na

Just adding: expect breakage if you do not routinely check 
/usr/ports/UPDATING before throwing portupgrade -a or portmaster -a at 
the new ports.

The ports team has really improved the situation, but once in a while 
there are still manual steps that must be taken before doing a mass 
upgrade of ports.

See http://www.wonkity.com/~wblock/docs/html/portupgrade.html for more 
detail.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1604161004330.46192>