Todd Vierling <tv@pobox.com> wrote:
>It already fails if the architecture or host OS doesn't match, so that you
>won't completely hose a system which is not appropriate for DESTDIR=/.  It
>would be nontrivial, but feasible, to add a check that the currently running
>kernel version >= the osrelease.sh version.  This would be the "most
>correct" fix....

Well, while we're discussing rope availability issues, note that there
are some (infrequent) occations when it isn't even necessary to build
a new kernel - for example, all of the changes that have gone into the
-1-5 branch since 1.5.3 have been library security patches, thus while
a full build was useful to make sure that any statically-linked
binaries were updated, a new kernel wasn't necessary...

(And managements tend to prefer to see a version number like 1.5.3
than one like 1.5.4_ALPHA - I though the whole stigma (not to mention
confusion with the alpha port) surrounding _ALPHA suffixes had led to
us getting rid of them, especially on release branches - with 1.5.3
(which was in _ALPHA at the time of the discussion) jumping to _RC1,
and 1.6 starting at _BETA1...)

jdarrow

-- 
John Darrow - Senior Technical Specialist               Office: 630/752-5201
Computing Services, Wheaton College, Wheaton, IL 60187  Fax:    630/752-5968
Pager via email: 6303160707@alphapage.airtouch.com      Pager:  630/316-0707
Email: John.P.Darrow@wheaton.edu (plain text please, no HTML or proprietary)