On Saturday 05 August 2006 19:16, cpghost wrote:
How do I get portmanager to upgrade ports, using
1. pre-built packages from /usr/ports/packages (ONLY),
and only if there's no binary package there,
2. build from source as usual?
Additional limit (preventing use of portupgrade -P) is
On Mon, Aug 07, 2006 at 10:24:48AM +0200, Jonathan McKeown wrote:
On Saturday 05 August 2006 19:16, cpghost wrote:
How do I get portmanager to upgrade ports, using
1. pre-built packages from /usr/ports/packages (ONLY),
and only if there's no binary package there,
2. build from
On Saturday 05 August 2006 18:16, cpghost wrote:
Building packages for multiple machines on a fast CPU,
with portmanager's -bu option populates a /usr/ports/packages tree.
So far, so good.
What I'd like though, is to be able to reuse that tree (mounted via
NFS or rsynced over) on other
On Mon, Aug 07, 2006 at 04:03:00PM +0100, RW wrote:
On Saturday 05 August 2006 18:16, cpghost wrote:
Building packages for multiple machines on a fast CPU,
with portmanager's -bu option populates a /usr/ports/packages tree.
So far, so good.
What I'd like though, is to be able to reuse
On Monday 07 August 2006 16:12, cpghost wrote:
On Mon, Aug 07, 2006 at 04:03:00PM +0100, RW wrote:
A key design feature of portmanager is that everything is built with
up-to-date dependencies, having this kind of feature would, in general,
defeat that.
Why would that? The port trees
On Mon, Aug 07, 2006 at 05:40:23PM +0100, RW wrote:
On Monday 07 August 2006 16:12, cpghost wrote:
On Mon, Aug 07, 2006 at 04:03:00PM +0100, RW wrote:
A key design feature of portmanager is that everything is built with
up-to-date dependencies, having this kind of feature would, in
Building packages for multiple machines on a fast CPU,
with portmanager's -bu option populates a /usr/ports/packages tree.
So far, so good.
What I'd like though, is to be able to reuse that tree (mounted via
NFS or rsynced over) on other machines with much slower CPUs.
The fast build machine and
