Deterministic package building with ports

[Peter Schuller]

> consistently. tinderbox I presume works, being used for official bulk

Scratch the bit about tindexbox; brain lapse.

But I also wanted to clarify that I specifically do not want to
perform in-place upgrading from source, because the intent is to have
a minimal time window during which the system is inoperative. In fact
the current procedure is do pkg_delete *all* packages and just
re-install. This is in fact fine (though it would be better to be able
to intelligently re-install only what is needed).

However note that I specifically do *not* want to play games with
trying to minimalistically upgrade only those things that specifically
are required according to dependency information. I gave up on this
years ago; it just doesn't work without some perfect mythological
ports tree. I specifically want to build packages from a snapshot of
the ports tree; I do not want to mix old/new software, regardless of
whether the dependency claims that some particular major version of a
library is supposed to be compatible. The intent is to effectively
build and deploy something which is as close as possible to what the
port maintainer/build cluster will have tested, at all times.

-- 
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller at infidyne.com>'
Key retrieval: Send an E-Mail to getpgpkey at scode.org
E-Mail: peter.schuller at infidyne.com Web: http://www.scode.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081203/3eb0b49b/attachment.pgp