Re: jhalfs and all installed packages on the system
"Pierre Labastie" ([email protected] via alfs-discuss Mailing List) <[email protected]> Thu, 18 Dec 2025 10:22:12 +0100
| Newsgroups | gmane.linux.lfs.automated |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1766049742-9714-50668 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 2025-12-18 at 02:36 -0300, Jamenson Espindula wrote: > Hi all. >=20 > I did use the jhalfs system to build some packages on my just built > Linux From Scratch (LFS) 12.4. >=20 > 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! >=20 > 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). >=20 > 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). >=20 > I tried to manually build the 'pcmanfm-qt-2.2.0' package, but with no > success (sorry for such a lack of information). >=20 > My goal with this message is to ask you: >=20 > 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. >=20 > 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. >=20 > 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 ------------=_1766049742-9714-50668 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 ------------=_1766049742-9714-50668--