| Newsgroups |
gmane.linux.lfs.beyond.devel |
| Message-ID |
<[email protected]> |
On Thu, 2025-10-02 at 12:01 -0500, Bruce Dubbs wrote:
> On 10/2/25 11:49 AM, Viel Losero ([email protected] via blfs-dev
> Mailing List) wrote:
> >
> > Hi all,
> >
> > This is my first post on the list.
> >
> > Fist of all, thanks all you for your great job.
> >
> > Second, sorry because English is not my main language.
> >
> > 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.
> >
> > Dunno if this happens with more XML elements and attributes.
> > Need look deeper. Did you accept patches? commits?
> > Or maybe some can fix it opening a ticket.
> > I need to learn how you works. :) I am old but new here.
> >
> > 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.
> >
> > There are any file that document the use of these attributes?
> > from my notes:
> > # mlfs book --> init
> > # mlfs chapter -->
> > # mlfs sect1 id="ch-tools-{pkg}" --> chroot package name
> > # mlfs sect1 id="ch-system-{pkg}" --> package name
> > # mlfs sect2 role="package" --> package description, build time and
> > disk space.
> > # mlfs sect2 role="nodump" --> commands related to config files,
> > tests ... no needed to run
> > # mlfs sect2 role="installation" --> patch, configure, make,
> > install and post
> > # mlfs sect2 role="configuration" --> package configuration files
> > like vimrc
> > # mlfs sect2 role="content" --> the last lines explain what in
> > package.
> > # mlfs sect2 arch="ml_32,ml_all" -->
> > # mlfs sect2 arch="ml_x32,ml_all" -->
> > # mlfs screen revision="sysv" -->
> > # mlfs screen revision="systemd" -->
> > # mlfs userinput remap="pre" --> patch, and post. like make
> > distclean.
> > # mlfs userinput remap="configure" --> configure the package
> > # mlfs userinput remap="make" --> make the package
> > # mlfs userinput remap="test" --> tests, exclude
> >
> > Some examples for userinput with and without remap="pre":
> > [root@dirty mlfs]# grep -rwn . -e ".*patch -Np1"
> > seems all matches have remap="pre" excluding
> > ./chapter03/packages.xml:508:
> > that not apply because is a note.
> > [root@dirty mlfs]# grep -rwn ../glfs/ -e ".*patch -Np1"
> > edited output:
> > ../glfs/archive/glibc.xml:77:<screen><userinput>patch -Np1 -i
> > ../glfs/shareddeps/security/glib2.xml:115:<screen><userinput
> > remap="pre">patch
> > [root@dirty mlfs]# grep -rwn ../blfs-git/ -e ".*patch -Np1"
> > edited output:
> > ../blfs-git/x/installing/mesa.xml:342:<screen><userinput>patch -Np1
> > -i
> > ../blfs-git/x/installing/xorg-server.xml:233:<screen><userinput
> > remap="pre">patch -Np1 -i ../xorg
>
> We recommend doing a manual build at least once before trying to
> automate building
> LFS/BLFS.
>
> The only reason we have the remap= attributes in the xml files is to
> support alfs:
> https://rivendell.linuxfromscratch.org/alfs/
>
> That tool is primarily for developers, but others find it useful.
FWIIW, only attributes that are referenced in "template/template.xml"
are used by alfs for BLFS. That is, any attribute in userinput tag is
not used by alfs (this is different in LFS, where remap attributes are
all in userinput tags). Having more attributes would help a lot (for
alfs and any automation tool), but would put too much burden on
editors, I guess. I'm not sure GLFS/MLFS should follow the template. If
they did, they could be tested with alfs, I think...
Pierre
--
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page