Re: jhalfs and all installed packages on the system

This is a multi-part message in MIME format...

------------=_1766117753-30781-50807
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Em qui., 18 de dez. de 2025 =C3=A0s 06:22, Pierre Labastie
<[email protected]> escreveu:
>
> On Thu, 2025-12-18 at 02:36 -0300, Jamenson Espindula wrote:
> > Hi all.
> >
> > I did use the jhalfs system to build some packages on my just built
> > Linux From Scratch (LFS) 12.4.
> >
> > The version of the jhalfs is recent. Unfortunately, I did something
> > not recommended: I selected all packages under the LXQt menu and ran
> > the tool! The result was a list of three hundred and twenty nine
> > (329)
> > packages to install!
> >
> > I had only two issues: a symbolic link had to be manually deleted (I
> > do not remember more details any more) and two Python modules had to
> > be manually built (I do not remember more details anymore too).
> >
> > However, the construction stopped at 'pcmanfm-qt-2.2.0'. The make
> > system had output that it has no target to run install (or something
> > like that).
> >
> > I tried to manually build the 'pcmanfm-qt-2.2.0' package, but with no
> > success (sorry for such a lack of information).
> >
> > My goal with this message is to ask you:
> >
> > One: am I really required to manually tell jhalfs about every single
> > installed package on the system or can it automatically determine
> > every single installed package on the system (with no human
> > intervention)?
>
> Not sure what you mean. Basically, there is no universal way to tell
> whether a package is installed on the system or not, so jhalfs cannot
> automatically find all installed packages. But jhalfs records each
> package it installs, so you'd better build jhalfs very early in the
> build process, or ideally build LFS with jhalfs and enable blfs tools.
> >
> > Two: once I told jhalfs about every single installed package, If a
> > given package that is already installed is a dependency of another
> > package that is yet to be installed, is it normal the system
> > reinstall
> > such a package?
>
> Yes and no. If the available version is newer than that of the
> installed package, then it will get rebuilt, otherwise, it shouldn't be
> rebuilt.
> >
> > Three: jhalfs could use the 'pkgconf' program in order to
> > automatically determine every single installed package on the system
> > (with no human intervention)?
>
> Xi has already answered this question.
>
>
> I must add that the dependency system of jhalfs is based on information
> given in the book, that it may fail sometimes (although rarely).
> Specially with LXQt, since there are two ways of installing the needed
> KDE packages, it may happen that the dependency system does not install
> the right ones.
>
> Now, for the pcmanfm-qt problem, I cannot answer without trying myself.
> You have to check the generated scriptlet, and find where it may fail.
> Also examine the logs...
>
> Regards
> Pierre
> --
> http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
> Unsubscribe: See the above information page

Thank you for your valuable answers guys!

I have another Linux From Scratch (LFS) system (version 12.2)
installed. It has a few packages beyond the basic LFS.

This time, I did use the jhalfs more carefully. I started building and
installing packages that do not have any dependencies (e.g.
Packaging-24.1, a Python module). I really figured out jhalfs recorded
that package as installed and it is not shown any more as a candidate
for installing.

Really, the jhalfs tool, as far as I can tell, works relatively well,
being an extremely valuable tool for building and installing LFS and
BLFS packages from source!

As of today, I understand the following general actions has to done in
order a person can use the tool:

Step one: access the 'blfs_root' directory;

Step two: update the records about all the installed packages (run
./update-installed.sh);

Step three: output the 'targets' for installation (run make);

Step four: access the working subdirectory (cd work);

Step five: output the updated 'Makefile' file (run ../gen-makefile.sh);

Step six: effectively build the requested packages (run make).

If any building package gets in trouble, then inspect the logs and
start over again.

That simple script helped me to understand the tool. Maybe help others too.

I would suggest putting that information inside the 'README.BLFS' file
(or another more suitable file).

Thank you once again!

Jamenson Espindula

------------=_1766117753-30781-50807
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0

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