That's a bit unfair! Most of my posts in this subforum have been technical advice to newbies who have run into problems with their build. I have not started any knocking threads; we have too many of those already in the Slackware subforum. But if someone else makes a point that I think is valid, I will say so.

If you are not 100 year old, just do what do you think is ok for you. Time ago I built myself LFS. It took me a week due to poor hardware. Did I learn something? Don't remember now. LFS I just bunch of recipes to follow. Like cooking a meal. It really impressive how fast it boots. But sometimes you just want to use system instead of sitting and thinking about failed build. Most people for this purpose have another distro. Plug and play.

YES, that is certainly doable. There are pages dedicated to that kind of project that are (in general) NOT LFS specific.

I do not really think you are ready for this, but if you want to resolve your doubts about creating an LFS installation the way to resolve that is to try! When you succeed, consider what you have learned and resolve to do it again after you have ten or twelve more years of experience. You will miss some lessons both times, but doing it twice with some time between to absorb the lessons and learn more about Linux and FOSS will teach you a lot!

Like others have said just build your first LFS and things will make sense as you go. SO many get ahead of themselves with their BIG ideas. GL.

To me, you are sort of describing Gentoo Linux. Have you tried that?

It has an amazing package management system called Portage that will handle the dependencies, mostly. And the packages are built from source code, mostly.

And yet there is still plenty for you to do to make you feel like you created something special. There are the so-called USE variables, and CPU flags, and license agreements, and masked packages...all of which require you to do things to tweak dependencies and build options. There may even be some circular dependencies that you may need to think through. All just like BLFS where you are mostly on your own, but with a lot of help from Portage in Gentoo. And most of that stuff you work out can be saved in special Portage directories so subsequent builds go even smoother.

There is a detailed Gentoo handbook to get you started, and a Wiki and forum for help.

I have been using BLFS for over ten years as the only operating system in the house. But I seem to have less time to maintain that thing or to rebuild it nowadays even though I use scripts to build it. I learned Gentoo in a few days and managed to build a twin to my BLFS system in two or three days in spare time.

I recommend that you (or anybody, really) look into Gentoo Linux.

Moin,

I totally understand Hazel. I also think it's either a toy or complicated to keep updated. Sad, but that's it.
Also it's not very portable; so i'd not recommend it for newbies to build LFS once and then distibute it on several, different PCs (I write this, because i just build last weekend an LFS-11 on a newer i3 system, which was totally unusable on an older i3 system (funny internal gcc compiler errors looking somehow related to floatingpoint)).
Also i'm not a big fan of the growing dependencies of packages, even circular dependencies. I'm not happy with rust, Python everywhere (including still Python2), PAM and fancy build tools, where it's not clear, which options were used during the last build (e.g. if the build has been done a few months ago, so the cmd line is not longer in history file).
And there are lots of more things, i dont like.
But anyway, i still like the idea behind B/LFS and i suspect the LFS Maintainers are not very happy with the things i mentioned either; and so it's still my choice for my PC. But i'm aware, that it's not the best choice for anybody.

cheers,
WK

LFS is very portable if you build it with a platform agnostic setup. That's for builders to fig out.
It's mentioned in the book. Updating is simple as overwriting pkgs with new versions. Only exception is the toolchain. Leave it alone or rebuild from beginning. Most issues/complaints are from users lacking skill and understanding.

1 members found this post helpful.

agreed i have recently started experimenting with a rock pi x, and my qt5 package from my desktop lfs runs fine on the rock, compiling qt5 nativly on it was not really an option, i have also ibstalled a few other binary packages from mymain lfs without problems, main lfs cpu is i3, rock is atom (i think ).

P.S.
sorry didn't mean to start a bit of a flame war

Are there any tips in order to make management of LFS any easier, like using ZFS for snapshots etc.

Snapshots have nothing to do with package management.
Use whatever method you want for building packages, managing them, etc.
A log to keep what you have installed does wonders. You could stay on a specific version of the (b)lfs-book so you can at least search what version of a specific piece of software you have installed.