Re: LFS Books homogenization

On 02-10, Zeckma wrote:
> On 10/2/25 10:49, Viel Losero ([email protected] via blfs-dev Mailing
> List) wrote:
> > Well, to explain it in short, looking a few inside the Book's XML files
> > I found that some Elements like userinput sometimes have the attribute
> > remap and some times not, in BLFS and GLFS. MLFS looks fine.
> >
> > I think this attributes was helfull to extract the command lines for
> people
> > that want to automate the build of some packages. I am trying to build my
> > dirty system based on LFS but this is an other history.
> >
> > I think this attributes was helfull to extract the command lines for
> people
> > that want to automate the build of some packages. I am trying to build my
> > dirty system based on LFS but this is an other history.
> 
> Hi Viel, I'm the one who created GLFS. I can at least explain why a lot
> of the XML in the book isn't attributed up to snuff.
> 
> GLFS deviated from BLFS, quite heavily. With that came a lot of needed
> changes, a lot of work, a lot of reorgizations and corrections. At some
> point, I realized that the book would be incompatible with jhalfs.
> Truthfully, I gave up making the XML as standard as it could be. I was
> both lazy in the beginning and in the end of the first rough draft of
> the book. I've gotten a lot better about that and have been trying to
> make the XML better over a year.

Thanks for the reply and explanation Zeckma,

To avoid me that same problem is why I asked if there is defined somewhere the
use of the attributes ... and plans to the future.

> 
> Automation eventually became something I want to support but don't have
> much time to work on, and unsure how GLFS can get there and what
> support would look like. I could start trying to make the XML properly
> attributed at the very least, although would take some time.
> 
> There have been some rough spots, where the dump-commands target
> generated scripts with a set of commands that shouldn't get ran by
> default, and I fixed up most of them now.
> 
> Another thing too is that while GLFS is listed on the main LFS website,
> it isn't really part of the BLFS fold as it were. Eventually, getting
> dedicated mailing lists would be good. But for now, if possible, GLFS
> issues should go at https://github.com/glfs-book/glfs/issues. In this
> case, it's mostly fine since it also affects BLFS, though BLFS I think
> is on more solid ground.
> 
> I'll make an issue over there so I don't forget.
> 
> - Zeckma

Nice to know, I am working in my dirty system but maybe I can get some time to
... if you want try to send you some commits to tag the book. I think is a job
I can do.
I can take MLFS attributes as template to work but will be much better to
talk about before to avoid have to redo the job.

IMO an atribute post was needed because; pre is used to make distclean and
prepare the m32 part, it is better to separe now the pre and post. Anyway let
me go deeper in the template that Pierre point me.

Viel.

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