On 22/06/2019 18:34, Bruce Dubbs via blfs-dev wrote: > On 6/22/19 11:05 AM, Pierre Labastie via blfs-dev wrote: >> On 22/06/2019 17:41, Bruce Dubbs via blfs-dev wrote: >>> On 6/22/19 8:24 AM, Pierre Labastie via blfs-dev wrote: >>>> On 22/06/2019 14:23, Bruce Dubbs via blfs-dev wrote: >>>>> On 6/22/19 2:03 AM, Pierre Labastie via blfs-dev wrote: >>>>>> On 21/06/2019 16:54, Bruce Dubbs via blfs-dev wrote: >>>>>>> On 6/21/19 2:15 AM, Pierre Labastie via blfs-dev wrote: >>>>>>>> On 21/06/2019 00:57, Bruce Dubbs via blfs-dev wrote: >>>>> >>>>>>> What I've done is to checkout the full repo: >>>>>>> >>>>>>> svn://svn.linuxfromscratch.org/BLFS >>>>>>> cd BLFS/branches/BOOK-elogind >>>>>>> make >>>>>>> >>>>>>> to get the book rendered. One of the problems is that BLFS/trunk/BOOK >>>>>>> is a >>>>>>> moving target. DJ has been merging trunk into elogind periodically and >>>>>>> it >>>>>>> needs to be done again. I think that after the next merge, you should >>>>>>> be >>>>>>> able >>>>>>> to start a test build and any changes to trunk after the test build >>>>>>> kicks >>>>>>> off >>>>>>> wouldn't materially affect the results. >>>>>>> >>>>>> >>>>>> As far as I understand, the merge is complete as of this morning (maybe >>>>>> missing node.js). I realize that jhalfs needs a tarball for >>>>>> blfs-bootscripts, >>>>>> which, as far as I know, does not exist yet for elogind. Would it be >>>>>> possible >>>>>> to create one, and have the elogind book point to it? I could (try to) do >>>>>> that, but it is maybe too early. >>>>> >>>>> It is not too early. The current trunk bootscripts work. That's what I >>>>> used >>>>> for my testing so far. The new bootscripts that are needed are there. >>>>> >>>>> I'm not sure how jhalfs accesses bootscripts, but a symlink in the tree >>>>> should >>>>> be enough. >>>> >>>> jhalfs accesses bootscripts by using the link to the tarball given on page >>>> "Chapter 2. Important Information/BLFS Boot Scripts". If this tarball >>>> contains >>>> the elogind bootscripts, all is well. But it does not seem to. As far as I >>>> can >>>> see, the blfs-bootscripts in trunk and in the bootscripts-elogind branch >>>> differ (diff attached). >>> >>> Fixed. This is one of the minor issues that will be coming up. If they are >>> all this easy, then we are in great shape. >>> >> >> Am I understanding correctly that the tarball will appear on anduin next >> night >> or so? > > It's not automatic. I just put it there.
OK, thanks. I think I'm all set up now... Will use latest kernel, but otherwise, book versions as of today. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
