Re: WebKitGTK known version to jhalfs and reversed dependency chain until poedit

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

------------=_1768976654-31461-56264
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, 2026-01-21 at 02:04 -0300, Jamenson Espindula wrote:
> Em ter., 20 de jan. de 2026 =C3=A0s 04:53, Jamenson Espindula
> <[email protected]> escreveu:
> >=20
> > I have decided to delete the whole 'webkitgtk-2.50.4' directory. I
> > unpacked it again and I began building the GTK-3 version.
> >=20
> After another twenty five build journey, the build of the GTK-3
> version was finished.
>=20
> Output of <grep 'pc'
> 2026-01-21-01-45-10-WebKitGTK-2.50.4-ninja_install.log.txt>:
>=20
> -- Installing: /usr/lib/pkgconfig/javascriptcoregtk-4.1.pc
> -- Installing: /usr/lib/pkgconfig/webkit2gtk-4.1.pc
> -- Installing: /usr/lib/pkgconfig/webkit2gtk-web-extension-4.1.pc
>=20
>=20
> Output of <free -m>:
>=20
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 total=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 used=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 free=C2=A0=
=C2=A0=C2=A0 shared
> buff/cache=C2=A0 available
> Mem.:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 7838=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 180=C2=A0=C2=A0=C2=A0=C2=A0 5=
927=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1827
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 7657
> Swap:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 999=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 3=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 996

It's meaningless to run free -m after building the package as the kernel
should have already reclaimed all the memory used for building the
package after the build finishes.  And it's also not so meaningful to
run this command at a random time point during the build process as the
RAM usage can change significantly in the different stages of the build.

Either write a script to run free -m and collect the maximum output
periodically during the build process, or put the build into a cgroup
and read memory.peak of that cgroup after the build instead.

--=20
Xi Ruoyao <[email protected]>

------------=_1768976654-31461-56264
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
------------=_1768976654-31461-56264--