[LFS Trac] #5785: Use kernel base+patch file

"LFS Trac" ([email protected] via lfs-book Mailing List) <[email protected]>
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.4
Component:  Book         |    Version:  git
 Severity:  normal       |   Keywords:
-------------------------+----------------------
 The kernel sources are provided either as a full tarball (which we are
 using currently) or as a base tarball plus a patch file. That is for
 example as base `linux-6.16.tar.xz` and the patch file `patch-6.16.1.xz`.

 Since kernel updates occur pretty frequent (weekly?), using the patch file
 variant would reduce the download size as it will not be required to
 retrieve over 150MB over and over again. The patch size of 6.16.1 is
 actually 200KB (of course increasing from version to version).

 In addition to saving some bytes on disk its a variant we do not have on
 any other package. I think it may be interesting to see how frequent
 updates can be handled without constantly retrieving the whole package
 file.

 Editing impact on the book is marginal - i've implemented that variant in
 the MLFS book as a POC.

 ---

 There are also patch files from x.y.z to x.y.(z+1). They are pretty small
 but using them would require to really use all of them, you cannot skip
 one. It does only make sence if you have a kernel source dir constantly
 unpacked and you want to follow every single release. Not partical for
 LFS, imho.
-- 
Ticket URL: <https://wiki.linuxfromscratch.org/lfs/ticket/5785>
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.