Date: Thu, 19 Jul 2007 10:57:05 -0700 From: "Michael S. Eubanks" <mse_software@charter.net> To: freebsd-questions@freebsd.org Subject: Re: portupgrade question Message-ID: <1184867825.2433.5.camel@yak.mseubanks.net> In-Reply-To: <200707191229.13618.freebsd@dfwlp.com> References: <200707191229.13618.freebsd@dfwlp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2007-07-19 at 12:29 -0500, Jonathan Horne wrote: > ive been using 'portupgrade -apP' on my systems lately (since i keep a central > repository of packages i build for my systems; a good bulk of them are used > across most/all of them). > > in situations where new packages are built from ports (ie, when the package > in /usr/ports/packages/All is no longer the most current), the -p is going > back and repackaging lots of packages that already exist. is there a way to > tell portupgrade not to repackage things that are not new versions? > > thanks, Don't use the ``p'' option. Use something like ``-afrRPv''. Force upgrade of all ports, their dependants and dependencies (recursively), build a package of the the newly compiled port, and do it verbosely. Or just use ``-arRPv'' if you do not want to rebuild or reinstall current ports (while still building packages). -Michael S. Eubanks mse_software@charter.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1184867825.2433.5.camel>