SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It can be done, but equally it's a pain in the ass to do so due to the amount of dependencies between release status packages.
Honestly, several of us considered it to perform audits of the sources at certain intervals, but after enough knowledge was shared, it was said to be implausible to do so.
Technically, all packages can be rebuilt against the system as-is, and many of us do so for private repos. However, for all intensive purposes, Slack from Scratch isn't advised or practical.
I imagine it might possibly be practical to build from scratch on a small, embedded platform where the hardware and workload never changes, but for a PC there is just no functional advantage.
For a new platform it's actually a must-have, but even then after enough time, packages will start pulling in more and more auto-detected dependencies and doing anything from scratch will become pointless.
Technically, a new platform is the ONLY time you should attempt a from scratch build of an existing OS.
LFS technically is a different beast of a distribution of Linux because it's geared more for research, education, and developmental purposes. You can use it as a functional distribution, but it does require, after enough time, that you learn package management techniques to some degree to be able to effectively manage the system and update packages.
Technically, a new platform is the ONLY time you should attempt a from scratch build of an existing OS.
not only
abi changes in the compiler or using a different compiler can be also a reason
does of course not happen very often (btw there is one abi change for g++ in the queue)
also it depends on the point of view
is a package that does not rebuild any more broken? some say yes (I for example), some say no.
to ensure that this is not the case you rebuild the world from time to time.
in embedded world if you just change the compiler for the same hardware is a full rebuild of everything for an existing platform is common (even if most fight changes but that's a different story). or add/change some libraries, you often change the config and build the full distribution to get a new image.
and I am pretty sure that there are more reasons
so the documented possibility to rebuild from scratch is a good one (and would spare sometimes a lot of work, arm port...)
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Original Poster
Rep:
Well, when I asked if anyone had tried and managed to build it from scratch, I thought there would be positive answers.
At that time, I had already built it twice. The first time I had written hand notes and it wasn't very clean, but I knew it was achievable.
By now I have tested it two more times and polished it a little bit.
The system you will get through this howto is not a complete slackware system, but a bootable slackware system with all the development tools you'll find in a LFS-7.7 system,and minimum network packages to access internet, but no X11 by now.
Location: Geneva - Switzerland ( Bordeaux - France / Montreal - QC - Canada)
Distribution: Slackware 14.2 - 32/64bit
Posts: 609
Rep:
Quote:
Originally Posted by nobodino
Well, when I asked if anyone had tried and managed to build it from scratch, I thought there would be positive answers.
At that time, I had already built it twice. The first time I had written hand notes and it wasn't very clean, but I knew it was achievable.
By now I have tested it two more times and polished it a little bit.
The system you will get through this howto is not a complete slackware system, but a bootable slackware system with all the development tools you'll find in a LFS-7.7 system,and minimum network packages to access internet, but no X11 by now.
Feel free to test it and enjoy as I did.
I just overview your doc, so I can't have an in depth "review", anyway, nice job !
Maybe an audit of the code was warranted after all. At least now we know several packages did need some fixes.
You still look at Slackware as a different kind of LFS. No package needs fixes - they all work. Slackware packages are not recompiled randomly: only when needed. And the mere fact that the current source does not compile any longer does not make it mandatory to recompile the package which works OK.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.