Re: [LFS Trac] #5785: Use kernel base+patch file
| Newsgroups | gmane.linux.lfs.book |
|---|---|
| Message-ID | <[email protected]> |
#5785: Use kernel base+patch file
-------------------------+-----------------------
Reporter: thomas | Owner: lfs-book
Type: enhancement | Status: new
Priority: normal | Milestone: 12.5
Component: Book | Version: git
Severity: normal | Resolution:
Keywords: |
-------------------------+-----------------------
Comment (by thomas):
no, you don't need all of them, just one as Xi already mentioned. When
starting with version 6.16 then you'll download `linux-6.16.tar.xz`.
Whenever a new kernel version appears, you do not need the full tarball of
lets say `linux-6.16.4.tar.xz` but just the `patch-6.16.4.xz`.
What you will do is
{{{
tar -xf linux-6.16.tar.xz
cd linux 6.16
xzcat ../patch-6.16.4.xz | patch -Np1
...
}}}
So, this variant is going from the base version (6.16) to the actual
version (6.16.4) in one step and this is what i'm talking about.
If you want to have a proper source tree laying around, then you might use
the __incremental__ patches which goes just one step ahead, lets say from
6.16.3 to 6.16.4. Assuming you have a source tree of 6.16.3 (either by
using linux-6.16.3.tar.xz or by linux-6.16.tar.xz+patch-6.16.3.xz), you
can simply do a
{{{
cd linux-6.16
xzcat ../patch-6.16.3-4.xz | patch -Np1
...
}}}
in the existing dir. It will then be on 6.16.4. With this, you can only
move one patch level further. When u need to go from 6.16.4 to 6.16.6,
you'll need the two __incremential__ patches 4-5 and the 5-6. But that is
not what we do in the book, we're doing a "unpack-build-delete", we do not
keep any source dir.
--
Ticket URL: <https://wiki.linuxfromscratch.org/lfs/ticket/5785#comment:9>
LFS Trac <https://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page