Re: Future automation possibilities

On Fri, Sep 30, 2022 at 7:52 PM Craig Jackson <[email protected]>
wrote:

> As someone who has attempted to implement this same concept in Python of
> reading the book XML and running commands as needed, It was incredibly
> difficult trying to triangulate the XML tree of the book to identify some
> sort of consistent pattern to use without also creating a lookup table for
> certain chapters which breaks forward compatibility when the book structure
> changes.  I understand that the book's XML is ideal for the context of
> publishing a document, so hesitation to change this is warranted.  But I
> wonder if a compromise would be for Jeremy or a delegate to provide a set
> of tags to the LFS dev team that would help to identify which type of text
> box is being used (run in chroot, run as lfs user, etc.) to provide that
> metadata for automation.
>

Sorry, I thought I replied to this, but it seems I only replied to Bruce
privately, unintentionally.

I think your notion about having standard tags in the book sources is spot
on. I dug through the LFS xml tonight, and I think it may not be as bad as
I initially thought. Most sect1's (pages) have an id that fits a consistent
naming pattern. It's usually `ch-preps-something` or `ch-tools-something`
or `ch-system-something`, at least as far as the ones jhalfs would be
concerned with. Then within those, most commands have a 'remap' attribute
that can be useful for classifying the actual commands.

I think there may be only one or two outliers that we might want to adjust.
BLFS, of course, is a different story, but I think we can probably attack
that one as a separate problem.

So, for example, one of the outliers is section 7.5, creating directories.
These commands are important for the build to do, and are probably not good
for jhalfs to hard-code within itself, but are currently indistinguishable
from example code that isn't meant to be run, like the example code for
capturing SBUs.

Also, looking more closely, there are some sections marked `ch-tools-*`
that are for outside of chroot, and some for inside chroot. If we could
distinguish between those two, it would help a lot. i.e., maybe
`ch-tools-*` and `ch-chroottools-*`? What would it take to get a change
like that in the book?

Thanks,

JH

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page