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: >>> Over the last couple of weeks I have been building a new version of LFS/BLFS >>> using DJ Lucas' elogind branch. With the addition of elogind and a few >>> other >>> changes, we will be able to add gnome to the System V version of the book. >>> >>> The process will look like this: >>> >>> a. Freeze update to the current svn version of the book. >>> b. Synchronize the current version into the elogind branch. >>> c. Move the current trunk to a branch >>> d. Move the elogind branch to the trunk, >>> e. Touch up titles, changelog, attribution, etc >>> >>> Individual scripts should continue to work for the most part, but some >>> instruction changes may be required. >>> >>> The systemd version of BLFS should be unchanged, but it's possible that some >>> of the System V changes may sneak in. >>> >>> I'll note that adding gnome is a lengthy task. Just building the required >>> and >>> recommended dependencies requires building about 325 packages after LFS is >>> complete. >>> >>> The timing of this change is being made now in order to have the entire >>> month >>> of July for testing and debugging before the August push for a September >>> release. >>> >>> My thought right now is to make the next LFS/BLFS version become 9.0 due to >>> the magnitude of the changes. >>> >>> Please post any questions or concerns on the blfs-dev mailing list (not >>> support). >>> >> >> Although they're not working as smoothly as I would like, the blfs tools for >> jhalfs allow to build a full blfs within a couple of days (or more, depending >> on the amount of time you accept to spend fixing scripts each day :). So, as >> soon as we have something close to the final version, I can test it. > > That would be great. We do need to make a couple of tweaks, but we should get > those done soon. > > 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. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
