Date: Sun, 26 Dec 2004 12:58:16 +0000 From: RW <list-freebsd-2004@morbius.sent.com> To: freebsd-questions@freebsd.org Subject: Re: portupgrade -P and local changes Message-ID: <200412261258.17222.list-freebsd-2004@morbius.sent.com> In-Reply-To: <20041226090451.2A69A54878@minnie.everett.org> References: <20041226090451.2A69A54878@minnie.everett.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 26 December 2004 09:04, Harlan Stenn wrote: > I have a couple of ports where I am using a Makefile.local to provide some > customizations for the local environment (I think they are for > postfix+SASL, and apache2+the experimental modules, but I could be > mistaken) where "stock" prebuilt packages are available. > > When I update the installed packages on the box, I like to use: > > portupgrade -Ppa > > The problem I have is that when these two ports get upgraded, portupgrade > fetches and installs the prebuilt packages, which means I have to remember > to then reinstall these two packages from the ports tree. > > Is there a way to tell portupgrade that it should not *fetch* prebuilt > ports for these two packages? If the packages are already there I'm fine > having them installed (as it means they were built using the Makefile.local > values and wrapped as a package from the -p flag). One thing you could do is enter them in HOLD_PKGS in pkgtools.conf, so that they wont be upgraded by portupgrade -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412261258.17222.list-freebsd-2004>