Once again, blocked:

https://sysdfree.wordpress.com/2023/07/08/372/

1 members found this post helpful.

I have not found a way to make Go slackbuilds reliably.

Even for Rust, I have a way to generate .info files for the downloads, which works in most cases:

https://gitlab.com/Lockywolf/lwfslac...ref_type=heads

This parses Cargo.lock, and is enough in most cases.

But for go, there is only half-baked solution (which is credited to Alexander):

https://gitlab.com/Lockywolf/lwfslac...ref_type=heads

1 members found this post helpful.

PHP 8.3.5
https://github.com/php/php-src/tags

There's standalone builds of udev being used in LFS and artix now:
https://www.linuxfromscratch.org/lfs...er08/udev.html
https://gitea.artixlinux.org/packages/udev

Any thoughts on trying a SlackBuild version in a similar style? Just wondering what will happen if eudev stalls out indefinitely. These distros have moved on it seems.

2 members found this post helpful.

Hi ,

postgresql is not good addition to php ?

Only a question.

I've been using PostgreSQL compiled from sources (now with hardening options) for my databases (for many years) without the slightest problem, including for Joomla.
Now Apache is compiled with support for MariaDB so it cannot be abandoned without changes to Apache.

3 members found this post helpful.

But some distros provide maridb and postgres ... and build apps using what he wants.

I sopossed postgresql is out cause is not hard dependecy , or cause mariadb works for php?

Going along the lines of "this because of that", Apache works great as a web server, but Nginx works great as a web server and quite a few more things. I haven't used PostgreSQL other than inside a few recent docker containers but if new things could be added to the extras/, I too would second PostgreSQL and nginx, aside of my previous speech for docker - just as sendmail is still there and works like a rock, while the main distro comes with postfix as its default.

2 members found this post helpful.

re: The "push, push, push" to switch from sysvinit over to systemd.

I love this redit post from 3yrs ago.

https://www.reddit.com/r/linux/comme...it.com%2Fembed

In 2095, Slackware will still be around and will still be on sysvinit.

1 members found this post helpful.

As long as people are able to extract (and maintain) the necessary modules from systemd. Why not

How many more will be needed in the future?
Does it make sense to have a large number of systemd modules (if not all), without systemd, just to say: we don't use systemd?

Yes !

4 members found this post helpful.

Since XZ 5.6.0 decompression uses the multi-thread by Default, I am afraid this increases the fragmentation of / (ext3) on my HDD when I use the package manager, is there any way to force the -T1 option only for the Slackware package manager?

Really?

If package have 1000 files you need write 1000 files.

Where is fragmentation?

You say me if write files 1 at time to write 1000 files are different than write as example 16 files per cycle ?

Fragmentation is when you write a lot and delete a lot ... but nothing arround write x1 or x10 , like delete x1 or x10.

Speed writing or deleting its same as writing and deleting slow .., is same space used/free.

I'm talking about the big files that will take several cycle.
I just say that I am frightened I not say that XZ did not work for limited fragmentation.
If courageous Current users can do tests on this

But why do you think this fragmentation is caused by xz (with or without multiple threads)?

The package manager simply calls xz to uncompress and sends the output from xz to stdin of tar. Would xz create some temporary files during parallell decompression?

If so, you might have some options to avoid such fragmentation:

1) Maybe that backdoored version of xz honors the TMPDIR variable for where to put any such temporary files? Pointing to a partition outside of the directory tree the package is being unpacked to would avoid fragmentation of the target partition.

2) installpkg has the options "-threads", if you set that to 1 it might solve your problem.

3) installpkg and those other tools for package management are really only simple scripts. If your really want to, you can edit them to do exactly as you like.

regards Henrik