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.
Is it feasible to remove QtAV from the default install? Upstream has ceased development, and it's taking the default spot for common formats such as MOVs.
Is it feasible to remove QtAV from the default install? Upstream has ceased development, and it's taking the default spot for common formats such as MOVs.
-- ltlnx
This QtAV is a hard dependency of Plasma5.
Which Plasma5 itself is on the verge of having ceased development, with the release of Plasma6 in the next 10 days.
Seems like QtAV was already removed on Oct 27 last year (as digikam doesn't require it anymore)! Sorry for the noise, I should've checked the ChangeLog...
stupid proposal for the name of the next Slackware.
Slackware-XV.I like 15.1 or
Slackware-XVI like 16, Xorg and V Init
****off topic****
Lockywolf
is that you are the maintainer of SBO:c-blosc and SBO:field3d?
the goal is to compile blender on Salckware?
have you a slackbuild for py-mathutils and OpenImageDenoise ?
Last edited by bigbadaboum; 02-20-2024 at 02:30 PM.
stupid proposal for the name of the next Salckware.
Salckware-XV.I like 15.1 or
Salckware-XVI like 16, Xorg and V Init
****off topic****
Lockywolf
is that you are the maintainer of SBO:c-blosc and SBO:field3d?
the goal is to compile blender on Salckware?
have you a slackbuild for py-mathutils and OpenImageDenoise ?
Does it make sense to add .orig to the list of filetypes ignored by run-parts? A patch applied by slackpkg could offer an update to, say, /etc/cron.daily/certwatch. When the slackpkg operator chooses (O)verwrite, certwatch becomes certwatch.orig but the executable bit is preserved. certwatch.new in turns becomes certwatch. At this point, run-parts starts running both scripts.
Code:
--- run-parts.orig 2021-02-13 10:57:35.000000000 +0000
+++ run-parts 2024-02-20 23:23:48.398624009 +0000
@@ -18,7 +18,7 @@
# There are several types of files that we would like to
# ignore automatically, as they are likely to be backups
# of other scripts:
-IGNORE_SUFFIXES="~ ^ , .bak .new .rpmsave .rpmorig .rpmnew .swp"
+IGNORE_SUFFIXES="~ ^ , .bak .new .orig .rpmsave .rpmorig .rpmnew .swp"
# Main loop:
for SCRIPT in $1/* ; do
stupid proposal for the name of the next Slackware.
Slackware-XV.I like 15.1 or
Slackware-XVI like 16, Xorg and V Init
****off topic****
Lockywolf
is that you are the maintainer of SBO:c-blosc and SBO:field3d?
the goal is to compile blender on Salckware?
have you a slackbuild for py-mathutils and OpenImageDenoise ?
Then maybe nxt after XVI would be W Slackware Wayland
Lockywolf
is that you are the maintainer of SBO:c-blosc and SBO:field3d?
the goal is to compile blender on Salckware?
have you a slackbuild for py-mathutils and OpenImageDenoise ?
Yes, I wanted to have Blender running with openvdb, but no, I don't have py-mathutils or openimagedenoise.
You can find all my slackware-related work on https://gitlab.com/Lockywolf/lwfslackbuilds
In the new hplip package, file /usr/lib64/cups/filter/hpcups links to libImageProcessor.so which is not found. The source tarball includes libImageProcessor-x86_64.so and libImageProcessor-x86_32.so binaries, not included in the -current hplip packages. Closed-source proprietary code?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
