Thanks for the report, Mark.
I've been building "vanilla Linux" for a couple of years and find
keeping the patches in order awfully difficult! I rely on time stamps,
which I occasionally have to adjust manually with 'touch'. I would
certainly ask the patch producers to
BE CAREFUL bout the time stamp(s) on the diff file(s)
I haven't been able to validate things on all HW,
but the packages I have employed and built work fully on both
mainframe Linux and PC class Linux. (PPC, PA, ARM, etc, I dunno!)
In any case, HW independence high on the list of important points.
Here I would ask the patch producers to
TAKE CARE that patches for one HW platform (zSeries)
do not break other HW platforms
Obviously, such breaks would be rejected by the larger community.
(Beyond the Linux/390 group.)
The accepted recipe is
download the source (possibly keep your own copy)
download any patches (possibly keep your own copies)
extract diffs from patch archives (see below)
explode the source (uncompress, untar)
apply patches
./configure
make
make install
Personally, I extract the diffs from the PATCH downloads
and use those as a restart point for patching. (I may or may not
keep the .tar.gz archive downloaded.) Not so for source: I usually
restart from the .tar.gz file for the SOURCE. (Because full source
is usually more stable and also large enough to warrant compression.)
Debian has their own tricks.
With SRPMs, there is yet another scheme.
Anything considered generic cannot use those:
must not break them, but should not require them either.
-- R;
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
