portupgrade -P and local changes

Harlan Stenn harlan at minnie.everett.org
Sun Dec 26 13:36:13 PST 2004


Yes, but that means I have to remember to build and package the ports
first, before I do anything else, and that implies I have to handle any
changed prerequisite packages as well.

If a way can be found to say "Do not fetch these packages" then this will
become a much easier process.

H
--
>> 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).

>Doesn't it use packages if they're present in the ${PACKAGES}
>directory (/usr/ports/packages by default)?


More information about the freebsd-questions mailing list