On 16 October 2017 at 16:55, Bruce Dubbs <[email protected]> wrote:
>> 2) Looking at both the sysv and systemd development books's "Appendix C. >> Dependencies" listing doesn't show any of those four packages listed >> as >> "Must be installed before systemd". Surely there must be such a >> requirement? > > It goes like this: > systemd needs meson and ninja > ninja needs python3 > python3 needs libffi OK, so the systemd book will show that eventually: good. >> 3) I note, that in both books, that the four new packages come right >> before systemd in the installation schedule, which just serves to >> increase the number of packages that appear to need to be installed >> BEFORE the sysv and systemd bullds diverge. But do packages such as >> Less, Gzip, Make, Patch, Tar and others actually need to come AFTER >> systemd has been installed ? > > At one time we tried to install in alphabetical order. That has faded over > the years as dependencies changed. > >> I appreciate that systemd pokes its fingers into a lot things but some >> of the packages that currently get built after systemd would appear to >> be systemd-unaware, so could they be built before systemd? > > Yes, but that really shouldn't be an issue. Exactly, and I'm thinking more in terms of making sure that LFS can serve as a way to highlight just how little needs to be "changed" to move from the one "init system" to the other. For me, systemd should be as far down the install chain as it's possible to get it, as then, as your comments re "old alphabetcial order" and "not an issue" suggest, the two books would only need to diverge much closer to the end of Chapter 6? Kevin -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
