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.
So we should move ffmpeg, *all* the gst-plugins-* packages, imagemagick, pipewire and pulseaudio into the x series? Those are just a few examples of things that are in L and use X11 libraries... if we look in series other than L we can find more obnoxious examples, such as dbus, and python.
The point I'm making is that for many packages (especially considering a criteria like "requires X") there is no correct "series" to place them in, which is why mostly things don't move. But in the case of zxing-cpp it's a newer package and was the only thing in the kde series that was needed outside of it, so it made sense to relocate it.
IMO, if a particular package "requires X", it should not be in L
nor in any directory other than kde, x, xap, xfce
Of-course any package that "requires KDE" certainly should be in KDE
and any package that "requires xfce" certainly should be in XFCE
There are no packages in KDE that requite XFCE
and there are no packages in XFCE that require KDE
a, ap, d, e, f, k, l & y should not contain any packages that require X
all packages that require X should be in kde, x, xap, xfce
vim is in ap exactly where it should be because it does not require X
vim-gvim is in xap exactly where it should be because it does require X
As a good example is ffmpeg .. you can use console ffmpeg , but ffplay needs /x to open window player.
Then ..where place it ?
/l
/x
/ap
/xap
?¿
mplayer can run with or without X ...
My request is simply cause is only a lib and headers , and need it out of /kde enviroment cause you can use gstreamer on xfce.
Wrong on both counts.
Do this... slackpkg remove x/*
Now see if either ffmpeg or mplayer will run at the CLI with nothing at-all from the x directory installed.
This is what happens...
root@glennmcc-i7:/# slackpkg remove x/*
Looking for x/* in package list. Please wait... DONE
//snip
root@glennmcc-i7:/# ffmpeg
ffmpeg: error while loading shared libraries: libdrm.so.2: cannot open shared object file: No such file or directory
root@glennmcc-i7:/# mplayer
mplayer: error while loading shared libraries: libfontconfig.so.1: cannot open shared object file: No such file or directory
The mplayer package is in xap exactly where it should be
ffmpeg should be moved from L into xap
zxing-cpp, qt5, gst, gtk and many others that are in L should be in either x or xap
In woff2, it'd be nice to have the binaries woff2_compress, woff2_decompress, and woff2_info included.
For some reason, the source's CMakeLists only installs the binaries if BUILD_SHARED_LIBS is off, even though the binaries seem to be always built. So I suppose they just need to be install -m 0755'd to /usr/bin.
IMHO there is no need to split out libraries requiring X to some other directory than /l. In short, the recommended way to install Slackware is to do a full install and with a full install it does not matter much from which directories all packages come. When doing something else than a full install it is up to the user to figure out all dependencies.
But what if someone doesn't want X? Maybe Slackware is installed on a machine with only a simple text serial terminal? Even on a machine with only a text console you might be able to login from the network with ssh. With ssh you have X forwarding functionality which allows you to run X applications on the machine with only a serial text console and display those windows on another networked machine. So X can be useful also on a machine with only a text console and no VGA graphics.
If, there for some reason would be found necessary to move libraries depending upon X to another directory than /l, I think a new directory should be created. Maybe that directory should be named /xl as we today have a /ap directory and a /xap directory.
IMHO there is no need to split out libraries requiring X to some other directory than /l. In short, the recommended way to install Slackware is to do a full install and with a full install it does not matter much from which directories all packages come. When doing something else than a full install it is up to the user to figure out all dependencies.
Well then, here's a new suggestion.
Eliminate the subdirs and just have _all_ of the packages in /slackware(64)
Also eliminate the options of menu/expert so that the _only_ way to install slackware is ALL-or-NOTHING.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
