Date: Mon, 04 Nov 2013 13:48:18 -0600 From: Mark Felder <feld@FreeBSD.org> To: freebsd-stable@freebsd.org Subject: Re: pkgng: how to upgrade a single port? Message-ID: <1383594498.25577.42855717.6980DEBA@webmail.messagingengine.com> In-Reply-To: <3884C60E-FFEC-413C-901E-631E2862984B@gromit.dlib.vt.edu> References: <527406D2.7010200@intertainservices.com> <1383336649.16326.41750369.298F8E9D@webmail.messagingengine.com> <1383337118.18823.41752849.2502EBFD@webmail.messagingengine.com> <CA%2BdUSyoUQB%2BgLM8g70y6mz7c%2BHSb3DJpVFvaENgm45VwcYVjQA@mail.gmail.com> <5277E53A.4090208@intertainservices.com> <CAOjFWZ4r-gWHd9k8F-T9sE1_5Qa0VVbqzxwYVZGazFf2b0k8VQ@mail.gmail.com> <3884C60E-FFEC-413C-901E-631E2862984B@gromit.dlib.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
I now understand what you guys are trying to do, so a suggestion on how to do it: 1) Use poudriere. Make sure you have your "default" ports tree and your "production" ports tree. You can test from the default ports tree, and have a snapshot-in-time of the ports tree called "production" 2) Install/deploy your packages, do your testing, etc etc. 3) When you've finalized a "set" of packages make sure you note the exact ports tree revision and your "production" ports tree stays frozen at that revision. Do not do blind updates of this ports tree. 4) When a security or feature update happens for a package you want to upgrade, update that single port to the latest revision. Example: cd /usr/local/poudriere/ports/production/www/apache22 && svn up 5) Now you can safely build apache22, and pkg upgrade / pkg install will ONLY update that port. No other dependencies have been touched. 6) Be very paranoid and test well. Make sure you know what you're doing and be very careful that the port you updated does not have any dependencies that it expects to be updated as well. Good luck.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1383594498.25577.42855717.6980DEBA>