SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's the same in /etc/profile.d/kde.csh. I've been using a couple of patches that check for the existence of the KDE4 directory to keep the path neat and tidy.
I personally would be all in favor for that (I am already using GnuPG 2.3.0 here), but please note that this is a development branch (as GnuPG 2.1 was in its time). As the stable 2.2 branch is expected to be maintained at least until december 2024, maybe Slackware-15 should be shipped with it instead?
--- rc.inet1.conf 2021-04-09 10:39:43.320849604 -0500
+++ rc.inet1.conf.new 2021-04-09 10:44:00.881610200 -0500
@@ -14,6 +14,11 @@
#
# Important note for IPv6 stateless auto configuration (SLAAC) users:
# From Slackware 15.0 onwards, you need to set USE_SLAAC[0]="yes" below.
+#
+# The previous method of using the NETMASK[0] field no longer exists.
+# Instead use CIDR notation in the IP address. For example,
+# IPADDRS[0]="192.168.1.10/24". When used the pkgtools netconfig tool
+# will automatically add the CIDR notation.
# =============================================================================
Building firefox/thunderbird against more system-libs brought some instability in former times. This seems to have improved as some problematic options were removed entirely, what's left is used by arch/gentoo/..., so these are probably to consider:
installpkg writes COMPRESSED PACKAGE SIZE and UNCOMPRESSED PACKAGE SIZE with a comma if an appropriate locale (like LANG=de_DE.utf8) is set during installation:
I think it would be better to normalize this with LC_ALL=C when setting COMPRESSED and UNCOMPRESSED. Currently i have a mixture of formattings with comma and dot in /var/lib/pkgtools/packages because LANG was sometimes de_DE and sometimes en_US.
By the way: mariadb still always overwrites /etc/security/user_map.conf on update, see here. The default file only contains comments, so there is no need to force an update of this file.
Last edited by Markus Wiesner; 04-10-2021 at 09:50 AM.
Can we remove the second compilation of emacs-no-x11 from the Emacs package's slackbuild? We can always pass the option '-nw' to regular Emacs' binary to get the same result. That's what I use myself for editing emails with Mutt and git commit messages. It works fine and would allow us to take advantage of pdumper again, which should make the program boot a little faster. (That option is currently removed in the SlackBuild.)
Can we remove the second compilation of emacs-no-x11 from the Emacs package's slackbuild? We can always pass the option '-nw' to regular Emacs' binary to get the same result. That's what I use myself for editing emails with Mutt and git commit messages. It works fine and would allow us to take advantage of pdumper again, which should make the program boot a little faster. (That option is currently removed in the SlackBuild.)
Nope, an emacs binary linked against X11 libraries wouldn't start on a non-X11 machine, and it's still a large use-case for Slackware.
Nope, an emacs binary linked against X11 libraries wouldn't start on a non-X11 machine, and it's still a large use-case for Slackware.
Have you tried what I suggested? Besides, I use Emacs outside of X every day, and it works by invoking the regular Emacs binary, not emacs-no-x11. As far as I know, the latter is only used in X when you need no X, which is exactly the same use-case that 'emacs -nw' covers.
I may be wrong, of course, but I think Emacs detects when it's running on X and when it's not. The compilation options are just there to make Emacs X-capable, not to force X on it. But, again, I'm willing to be proved wrong. Test it and come back to me with the results. It's not like it's that big of an issue. I just wanted to remove bloat. If it can't be removed, so be it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.