On 08/21/2018 04:21 AM, Thomas Trepl wrote:
Am Montag, den 20.08.2018, 10:25 -0500 schrieb Bruce Dubbs:
On 08/20/2018 07:18 AM, Thomas Trepl wrote:
Am Mittwoch, den 15.08.2018, 21:25 -0500 schrieb DJ Lucas:
...
While creating a ticket for a minor bug in the Makefile, i saw that
linux-4.18.3 is targeted for LFS-8.4. Is that by intention or
shouldn't L1TF-stuff go into the upcoming LFS-release (as well as
the
e2fsprogs)?
Which makefile? You are always free to create a ticket for anything.
The Makefile to create the book. I've opened a ticket (#4339) on it.
Note that this is more of cosmetic kind, minor inconsistence than a
real bug.
Note that we always say to use the latest point version of the
kernel,
in this example 4.18.x. If you look at the dates for kernel releases
https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/
you'll see by our scheduled release date that we will be up to at
least
4.18.5. See that for 4.17 the e were 18 releases in 49 days.
Yes, sure. My thought was that when releasing a book version, we mark
some sort of "milestone" and while we are doing that, we know that
there are critical bugfixes to one of the most important packages but
do not include them. Someone who is building LFS using the stable
version 8.3 will miss the fixes if following the written text. Yes we
note that there may be newer kernels out there and user should use
them, but does it cost us really much to upgrade the kernel version
until release date has come?
Does it make sense to release an -rc every time the kernel changes while
we are in the middle of validating BLFS? I'll probably update the kernel
one more time at stable release.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
