LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-13-2020, 08:21 PM   #1
burning
Member
 
Registered: Jan 2020
Location: Canada
Distribution: Slackware
Posts: 172

Rep: Reputation: Disabled
How to move all user installed packages to my home partition?


I was installing some packages and I ended up using up 100% of the hard drive space in my root partition. I'd like to move any and all non-default packages I've installed into my home partition. Is this doable? As well as making it so any future packages I install will install there as well?

My partition scheme is as follows:
/dev/sda1 -boot
/dev/sda2 -swap
/dev/sda3 -extended
/dev/sda5 -root - within sda3
/dev/sda6 -home - within sda3
 
Old 07-13-2020, 09:10 PM   #2
EdGr
Member
 
Registered: Dec 2010
Location: California, USA
Distribution: I run my own OS
Posts: 419

Rep: Reputation: 205Reputation: 205Reputation: 205
Programs generally can't be moved because they have the pathnames of auxiliary files compiled into them.

You can either make a bigger root partition or recompile the programs to use a different path. ~/.local is a good choice for programs used only by you.
Ed
 
1 members found this post helpful.
Old 07-13-2020, 10:17 PM   #3
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,578
Blog Entries: 1

Rep: Reputation: Disabled
You need to create copy of directory structure - so you need $HOME/usr, $HOME/usr/bin etc. And put $HOME/usr/bin, $HOME/usr/sbin in your $PATH. Just look at /usr/local - you should have exactly the same directory structure in your $HOME as /usr/local.
Code:
piotr[~]$ ls /usr/local/
bin  etc  games  include  info	lib  man  sbin	share  src
Edit: I forgot, here from installpkg manual
Code:
 --root /otherroot
              Install  using a location other than / (the default) as the root
              of the filesystem to install on.   In  the  example  given,  use
              /otherroot  instead.  Setting the ROOT environment variable does
              the same thing.
It is as SBo packages are created - after compilation they are installed in some place - on my computer it is /tmp/SBo - then archived. If you share computer with others it is good idea to require personal binaries go under $HOME - just don't mess with system.

Last edited by igadoter; 07-13-2020 at 10:28 PM.
 
1 members found this post helpful.
Old 07-13-2020, 10:56 PM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
Installed packages are installed based on the file structure within the package. As Ed mentioned, installing them to another place may cause breakage without recompiling the package. As igadoter shows, there is an option for installpkg for you to specify installing to a different location, but if the packages rely on absolute locations, it'll likely lead to broken packages. You'd need to compile the packages to be installed in other directions, and SBo doesn't make it an easy to change option. You'd need to manually modify each and every SlackBuild to install to that new location.

If you just want to save the resulting packages (which are typically stored in /tmp/, they can easily be moved to wherever is best for you.
 
1 members found this post helpful.
Old 07-14-2020, 01:32 AM   #5
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,578
Blog Entries: 1

Rep: Reputation: Disabled
Quote:
Originally Posted by bassmadrigal
You'd need to compile the packages to be installed in other directions, and SBo doesn't make it an easy to change option. You'd need to manually modify each and every SlackBuild to install to that new location.
All SBo packages I built were installed at first under /tmp/SBo. So it is pure clean they cannot rely on fixed location in system. If that would be case the only way to run them is to keep them all constantly under /tmp/SBo - this is installation directory being set during compilation. Maybe there applications which looks up for full path - but I don't think these are SBo packages. It is easy just pick up any SBo package at hand and install it with installpkg under /usr/locale. Will see does it work or not. It is just advised to install under /usr. Essentially as for me good idea is separate partition under /usr/locale - the place where additional software, packages go. Just one look under /usr/local and one sees what is out of Slackware. System cleanup now means clean /usr/local. It is also convenient in case someone don't want to go with packaging. Just ./configure ; make ; sudo make install. Usually config script contains /usr/local as installation directory as default.

Last edited by igadoter; 07-14-2020 at 01:38 AM.
 
Old 07-14-2020, 01:45 AM   #6
kgha
Member
 
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 319

Rep: Reputation: 234Reputation: 234Reputation: 234
If I understand your situation correctly you're running out of space in /dev/sda1 but have plenty of space left in /dev/sda3. In that case, the simplest solution would be to shrink /dev/sda3, move /dev sda2, and then increase the size of /dev/sda1 accordingly. GParted will do that for you. You will get a warning that resizing the boot partition may break your install, but in practice it should work out fine, I've done this more than once without any issues.
 
1 members found this post helpful.
Old 07-14-2020, 02:44 AM   #7
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,578
Blog Entries: 1

Rep: Reputation: Disabled
Manually it would be difficult to achive moving files which belongs to package. But if you have a look at
Code:
$ less /var/log/packages
there are log files which contains location information
Code:
$ piotr[~]$ less /var/log/packages/compton-i586-1_SBo
FILE LIST:
./
install/
install/doinst.sh
install/slack-desc
usr/
usr/bin/
usr/bin/compton
usr/bin/compton-trans
usr/doc/
......
you can use such descritpion to effectively move all files to another location say
Code:
$ while read file ; do cp -a /"$file" $HOME ; done < my-compton-i586-1_SBo
if things are ok - I mean application runs - you can now delete files from original location. But first you need to filter log file to remove some parts eg. lines which ends with /, say
Code:
grep -v /$ compton-i586-1_SBo > my-compton-i586-1_SBo
I hope this will help.
 
1 members found this post helpful.
Old 07-14-2020, 05:03 AM   #8
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,240

Rep: Reputation: 518Reputation: 518Reputation: 518Reputation: 518Reputation: 518Reputation: 518
You are better off just resizing your partitions if you can. Been there done that.

This is my simple layout:
Code:
$ df -ht ext4
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        98G   26G   67G  28% /
/dev/sda3       818G  318G  459G  41% /home
Plenty of room on / for growth.
 
1 members found this post helpful.
Old 07-14-2020, 10:24 AM   #9
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
Quote:
Originally Posted by igadoter View Post
All SBo packages I built were installed at first under /tmp/SBo. So it is pure clean they cannot rely on fixed location in system. If that would be case the only way to run them is to keep them all constantly under /tmp/SBo - this is installation directory being set during compilation. Maybe there applications which looks up for full path - but I don't think these are SBo packages. It is easy just pick up any SBo package at hand and install it with installpkg under /usr/locale. Will see does it work or not. It is just advised to install under /usr. Essentially as for me good idea is separate partition under /usr/locale - the place where additional software, packages go. Just one look under /usr/local and one sees what is out of Slackware. System cleanup now means clean /usr/local. It is also convenient in case someone don't want to go with packaging. Just ./configure ; make ; sudo make install. Usually config script contains /usr/local as installation directory as default.
The programs aren't designed to run out of /tmp/SBo. That is strictly the staging directory for packaging (if you look at SlackBuilds, they use something similar to this for compilation:

Code:
./configure \
  --prefix=/usr \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
  --sysconfdir=/etc \
  --localstatedir=/var \
  --mandir=/usr/man \
  --docdir=/usr/doc/$PRGNAM-$VERSION \
  --disable-static \
  --build=$ARCH-slackware-linux
The --prefix option tells ./configure where the program is intended to be installed to. This is an absolute location. If you wanted it installed in /usr/local/ or ~/programs, you'd need to adjust the --prefix option to do that. The /usr prefix is hardcoded into the SlackBuild, so if you want to change it, you have to manually edit the SlackBuild to do so (vs passing an updated VERSION variable if you want to do a version bump).

What allows the programs to be staged in a separate directory is the following line, which installs the program after the compilation has completed:

Code:
make install DESTDIR=$PKG
This will run the install, but will add the $PKG variable before all the install locations. This allows things to be installed in a separate, standalone directory that allows for easy packaging. While some programs might run in the /tmp/SBo folder, many won't. For example, if we look at picard, if you try to run it from /tmp/SBo/package-picard without it being installed, you'll get the following error, because it's looking for the picard python module in a hardcoded location:

Code:
jbhansen@craven-moorhead:/tmp/SBo$ package-picard/usr/bin/picard 
Traceback (most recent call last):
  File "package-picard/usr/bin/picard", line 2, in <module>
    from picard.tagger import main; main('/usr/share/locale', True)
ModuleNotFoundError: No module named 'picard'
 
3 members found this post helpful.
Old 07-15-2020, 05:34 AM   #10
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,578
Blog Entries: 1

Rep: Reputation: Disabled
I understand. But you can still omit limitations with symbolic links. Point it to needed library which can be kept anywhere.

Last edited by igadoter; 07-15-2020 at 06:23 AM.
 
Old 07-15-2020, 07:35 AM   #11
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 9,672

Rep: Reputation: 4316Reputation: 4316Reputation: 4316Reputation: 4316Reputation: 4316Reputation: 4316Reputation: 4316Reputation: 4316Reputation: 4316Reputation: 4316Reputation: 4316
Just going to point out that the "--root" option to installpkg is for setting up a chroot. If you want to use it for anything else, well, you're going to have to be the first to try it.

Oh, and the syntax is "installpkg --root PATH", not "installpkg --root=PATH". I've hosed my system with this mistake

Last edited by dugan; 07-15-2020 at 07:51 AM.
 
1 members found this post helpful.
Old 07-15-2020, 07:53 AM   #12
sevendogsbsd
Senior Member
 
Registered: Sep 2017
Distribution: Slackware
Posts: 1,938

Rep: Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841
I hate threads where OP lobs a question out there and then vanishes. Guess they got the answers they needed but would be nice for them to thank the folks that helped them, or at least provide some sort of response.
 
1 members found this post helpful.
Old 07-15-2020, 09:16 AM   #13
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,578
Blog Entries: 1

Rep: Reputation: Disabled
Thread is marked as solved. But for me is ok. I learned quite a lot. Say now I am convinced to create my own packages. With my own flavour but essentially follwing sbo.
 
Old 07-15-2020, 09:51 AM   #14
sevendogsbsd
Senior Member
 
Registered: Sep 2017
Distribution: Slackware
Posts: 1,938

Rep: Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841
Creating packages is easy but I did not understand why OP wanted to install them to their /home directory. That made no sense to me. To each, his/her own though
 
Old 07-15-2020, 10:44 AM   #15
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
Quote:
Originally Posted by igadoter View Post
I understand. But you can still omit limitations with symbolic links. Point it to needed library which can be kept anywhere.
That could require a large amount of symbolic links depending on the package. Could you imagine trying to symlink everything needed to properly run qt5? There would be some directories you could symlink, but all these libs in /usr/lib{,64} would need to be manually symlinked. You might be able to prevent needing to symlink these by using LD_PRELOAD. But I certainly wouldn't want to take the time and try and fix all the issues that would crop up from installing a package designed to be in /usr/ to some random directory on the system. It would be much easier to just rebuild the program setting a new prefix or resizing my partitions (if possible) to provide me more space in the partition containing /usr/

Code:
/usr/lib64/libQt53DAnimation.la
/usr/lib64/libQt53DAnimation.prl
/usr/lib64/libQt53DAnimation.so.5.9.7
/usr/lib64/libQt53DCore.la
/usr/lib64/libQt53DCore.prl
/usr/lib64/libQt53DCore.so.5.9.7
/usr/lib64/libQt53DExtras.la
/usr/lib64/libQt53DExtras.prl
/usr/lib64/libQt53DExtras.so.5.9.7
/usr/lib64/libQt53DInput.la
/usr/lib64/libQt53DInput.prl
/usr/lib64/libQt53DInput.so.5.9.7
/usr/lib64/libQt53DLogic.la
/usr/lib64/libQt53DLogic.prl
/usr/lib64/libQt53DLogic.so.5.9.7
/usr/lib64/libQt53DQuick.la
/usr/lib64/libQt53DQuick.prl
/usr/lib64/libQt53DQuick.so.5.9.7
/usr/lib64/libQt53DQuickAnimation.la
/usr/lib64/libQt53DQuickAnimation.prl
/usr/lib64/libQt53DQuickAnimation.so.5.9.7
/usr/lib64/libQt53DQuickExtras.la
/usr/lib64/libQt53DQuickExtras.prl
/usr/lib64/libQt53DQuickExtras.so.5.9.7
/usr/lib64/libQt53DQuickInput.la
/usr/lib64/libQt53DQuickInput.prl
/usr/lib64/libQt53DQuickInput.so.5.9.7
/usr/lib64/libQt53DQuickRender.la
/usr/lib64/libQt53DQuickRender.prl
/usr/lib64/libQt53DQuickRender.so.5.9.7
/usr/lib64/libQt53DQuickScene2D.la
/usr/lib64/libQt53DQuickScene2D.prl
/usr/lib64/libQt53DQuickScene2D.so.5.9.7
/usr/lib64/libQt53DRender.la
/usr/lib64/libQt53DRender.prl
/usr/lib64/libQt53DRender.so.5.9.7
/usr/lib64/libQt5AccessibilitySupport.a
/usr/lib64/libQt5AccessibilitySupport.la
/usr/lib64/libQt5AccessibilitySupport.prl
/usr/lib64/libQt5Bluetooth.la
/usr/lib64/libQt5Bluetooth.prl
/usr/lib64/libQt5Bluetooth.so.5.9.7
/usr/lib64/libQt5Bootstrap.a
/usr/lib64/libQt5Bootstrap.la
/usr/lib64/libQt5Bootstrap.prl
/usr/lib64/libQt5Charts.la
/usr/lib64/libQt5Charts.prl
/usr/lib64/libQt5Charts.so.5.9.7
/usr/lib64/libQt5Concurrent.la
/usr/lib64/libQt5Concurrent.prl
/usr/lib64/libQt5Concurrent.so.5.9.7
/usr/lib64/libQt5Core.la
/usr/lib64/libQt5Core.prl
/usr/lib64/libQt5Core.so.5.9.7
/usr/lib64/libQt5DBus.la
/usr/lib64/libQt5DBus.prl
/usr/lib64/libQt5DBus.so.5.9.7
/usr/lib64/libQt5DataVisualization.la
/usr/lib64/libQt5DataVisualization.prl
/usr/lib64/libQt5DataVisualization.so.5.9.7
/usr/lib64/libQt5Designer.la
/usr/lib64/libQt5Designer.prl
/usr/lib64/libQt5Designer.so.5.9.7
/usr/lib64/libQt5DesignerComponents.la
/usr/lib64/libQt5DesignerComponents.prl
/usr/lib64/libQt5DesignerComponents.so.5.9.7
/usr/lib64/libQt5DeviceDiscoverySupport.a
/usr/lib64/libQt5DeviceDiscoverySupport.la
/usr/lib64/libQt5DeviceDiscoverySupport.prl
/usr/lib64/libQt5EglFSDeviceIntegration.la
/usr/lib64/libQt5EglFSDeviceIntegration.prl
/usr/lib64/libQt5EglFSDeviceIntegration.so.5.9.7
/usr/lib64/libQt5EglFsKmsSupport.la
/usr/lib64/libQt5EglFsKmsSupport.prl
/usr/lib64/libQt5EglFsKmsSupport.so.5.9.7
/usr/lib64/libQt5EglSupport.a
/usr/lib64/libQt5EglSupport.la
/usr/lib64/libQt5EglSupport.prl
/usr/lib64/libQt5EventDispatcherSupport.a
/usr/lib64/libQt5EventDispatcherSupport.la
/usr/lib64/libQt5EventDispatcherSupport.prl
/usr/lib64/libQt5FbSupport.a
/usr/lib64/libQt5FbSupport.la
/usr/lib64/libQt5FbSupport.prl
/usr/lib64/libQt5FontDatabaseSupport.a
/usr/lib64/libQt5FontDatabaseSupport.la
/usr/lib64/libQt5FontDatabaseSupport.prl
/usr/lib64/libQt5Gamepad.la
/usr/lib64/libQt5Gamepad.prl
/usr/lib64/libQt5Gamepad.so.5.9.7
/usr/lib64/libQt5GlxSupport.a
/usr/lib64/libQt5GlxSupport.la
/usr/lib64/libQt5GlxSupport.prl
/usr/lib64/libQt5Gui.la
/usr/lib64/libQt5Gui.prl
/usr/lib64/libQt5Gui.so.5.9.7
/usr/lib64/libQt5Help.la
/usr/lib64/libQt5Help.prl
/usr/lib64/libQt5Help.so.5.9.7
/usr/lib64/libQt5InputSupport.a
/usr/lib64/libQt5InputSupport.la
/usr/lib64/libQt5InputSupport.prl
/usr/lib64/libQt5KmsSupport.a
/usr/lib64/libQt5KmsSupport.la
/usr/lib64/libQt5KmsSupport.prl
/usr/lib64/libQt5LinuxAccessibilitySupport.a
/usr/lib64/libQt5LinuxAccessibilitySupport.la
/usr/lib64/libQt5LinuxAccessibilitySupport.prl
/usr/lib64/libQt5Location.la
/usr/lib64/libQt5Location.prl
/usr/lib64/libQt5Location.so.5.9.7
/usr/lib64/libQt5Multimedia.la
/usr/lib64/libQt5Multimedia.prl
/usr/lib64/libQt5Multimedia.so.5.9.7
/usr/lib64/libQt5MultimediaQuick_p.la
/usr/lib64/libQt5MultimediaQuick_p.prl
/usr/lib64/libQt5MultimediaQuick_p.so.5.9.7
/usr/lib64/libQt5MultimediaWidgets.la
/usr/lib64/libQt5MultimediaWidgets.prl
/usr/lib64/libQt5MultimediaWidgets.so.5.9.7
/usr/lib64/libQt5Network.la
/usr/lib64/libQt5Network.prl
/usr/lib64/libQt5Network.so.5.9.7
/usr/lib64/libQt5NetworkAuth.la
/usr/lib64/libQt5NetworkAuth.prl
/usr/lib64/libQt5NetworkAuth.so.5.9.7
/usr/lib64/libQt5Nfc.la
/usr/lib64/libQt5Nfc.prl
/usr/lib64/libQt5Nfc.so.5.9.7
/usr/lib64/libQt5OpenGL.la
/usr/lib64/libQt5OpenGL.prl
/usr/lib64/libQt5OpenGL.so.5.9.7
/usr/lib64/libQt5OpenGLExtensions.a
/usr/lib64/libQt5OpenGLExtensions.la
/usr/lib64/libQt5OpenGLExtensions.prl
/usr/lib64/libQt5PacketProtocol.a
/usr/lib64/libQt5PacketProtocol.la
/usr/lib64/libQt5PacketProtocol.prl
/usr/lib64/libQt5PlatformCompositorSupport.a
/usr/lib64/libQt5PlatformCompositorSupport.la
/usr/lib64/libQt5PlatformCompositorSupport.prl
/usr/lib64/libQt5Positioning.la
/usr/lib64/libQt5Positioning.prl
/usr/lib64/libQt5Positioning.so.5.9.7
/usr/lib64/libQt5PrintSupport.la
/usr/lib64/libQt5PrintSupport.prl
/usr/lib64/libQt5PrintSupport.so.5.9.7
/usr/lib64/libQt5Purchasing.la
/usr/lib64/libQt5Purchasing.prl
/usr/lib64/libQt5Purchasing.so.5.9.7
/usr/lib64/libQt5Qml.la
/usr/lib64/libQt5Qml.prl
/usr/lib64/libQt5Qml.so.5.9.7
/usr/lib64/libQt5QmlDebug.a
/usr/lib64/libQt5QmlDebug.la
/usr/lib64/libQt5QmlDebug.prl
/usr/lib64/libQt5QmlDevTools.a
/usr/lib64/libQt5QmlDevTools.la
/usr/lib64/libQt5QmlDevTools.prl
/usr/lib64/libQt5Quick.la
/usr/lib64/libQt5Quick.prl
/usr/lib64/libQt5Quick.so.5.9.7
/usr/lib64/libQt5QuickControls2.la
/usr/lib64/libQt5QuickControls2.prl
/usr/lib64/libQt5QuickControls2.so.5.9.7
/usr/lib64/libQt5QuickParticles.la
/usr/lib64/libQt5QuickParticles.prl
/usr/lib64/libQt5QuickParticles.so.5.9.7
/usr/lib64/libQt5QuickTemplates2.la
/usr/lib64/libQt5QuickTemplates2.prl
/usr/lib64/libQt5QuickTemplates2.so.5.9.7
/usr/lib64/libQt5QuickTest.la
/usr/lib64/libQt5QuickTest.prl
/usr/lib64/libQt5QuickTest.so.5.9.7
/usr/lib64/libQt5QuickWidgets.la
/usr/lib64/libQt5QuickWidgets.prl
/usr/lib64/libQt5QuickWidgets.so.5.9.7
/usr/lib64/libQt5RemoteObjects.la
/usr/lib64/libQt5RemoteObjects.prl
/usr/lib64/libQt5RemoteObjects.so.5.9.7
/usr/lib64/libQt5Script.la
/usr/lib64/libQt5Script.prl
/usr/lib64/libQt5Script.so.5.9.7
/usr/lib64/libQt5ScriptTools.la
/usr/lib64/libQt5ScriptTools.prl
/usr/lib64/libQt5ScriptTools.so.5.9.7
/usr/lib64/libQt5Scxml.la
/usr/lib64/libQt5Scxml.prl
/usr/lib64/libQt5Scxml.so.5.9.7
/usr/lib64/libQt5Sensors.la
/usr/lib64/libQt5Sensors.prl
/usr/lib64/libQt5Sensors.so.5.9.7
/usr/lib64/libQt5SerialBus.la
/usr/lib64/libQt5SerialBus.prl
/usr/lib64/libQt5SerialBus.so.5.9.7
/usr/lib64/libQt5SerialPort.la
/usr/lib64/libQt5SerialPort.prl
/usr/lib64/libQt5SerialPort.so.5.9.7
/usr/lib64/libQt5ServiceSupport.a
/usr/lib64/libQt5ServiceSupport.la
/usr/lib64/libQt5ServiceSupport.prl
/usr/lib64/libQt5Sql.la
/usr/lib64/libQt5Sql.prl
/usr/lib64/libQt5Sql.so.5.9.7
/usr/lib64/libQt5Svg.la
/usr/lib64/libQt5Svg.prl
/usr/lib64/libQt5Svg.so.5.9.7
/usr/lib64/libQt5Test.la
/usr/lib64/libQt5Test.prl
/usr/lib64/libQt5Test.so.5.9.7
/usr/lib64/libQt5TextToSpeech.la
/usr/lib64/libQt5TextToSpeech.prl
/usr/lib64/libQt5TextToSpeech.so.5.9.7
/usr/lib64/libQt5ThemeSupport.a
/usr/lib64/libQt5ThemeSupport.la
/usr/lib64/libQt5ThemeSupport.prl
/usr/lib64/libQt5UiTools.a
/usr/lib64/libQt5UiTools.la
/usr/lib64/libQt5UiTools.prl
/usr/lib64/libQt5WebChannel.la
/usr/lib64/libQt5WebChannel.prl
/usr/lib64/libQt5WebChannel.so.5.9.7
/usr/lib64/libQt5WebEngine.la
/usr/lib64/libQt5WebEngine.prl
/usr/lib64/libQt5WebEngine.so.5.9.7
/usr/lib64/libQt5WebEngineCore.la
/usr/lib64/libQt5WebEngineCore.prl
/usr/lib64/libQt5WebEngineCore.so.5.9.7
/usr/lib64/libQt5WebEngineWidgets.la
/usr/lib64/libQt5WebEngineWidgets.prl
/usr/lib64/libQt5WebEngineWidgets.so.5.9.7
/usr/lib64/libQt5WebSockets.la
/usr/lib64/libQt5WebSockets.prl
/usr/lib64/libQt5WebSockets.so.5.9.7
/usr/lib64/libQt5WebView.la
/usr/lib64/libQt5WebView.prl
/usr/lib64/libQt5WebView.so.5.9.7
/usr/lib64/libQt5Widgets.la
/usr/lib64/libQt5Widgets.prl
/usr/lib64/libQt5Widgets.so.5.9.7
/usr/lib64/libQt5X11Extras.la
/usr/lib64/libQt5X11Extras.prl
/usr/lib64/libQt5X11Extras.so.5.9.7
/usr/lib64/libQt5XcbQpa.la
/usr/lib64/libQt5XcbQpa.prl
/usr/lib64/libQt5XcbQpa.so.5.9.7
/usr/lib64/libQt5Xml.la
/usr/lib64/libQt5Xml.prl
/usr/lib64/libQt5Xml.so.5.9.7
/usr/lib64/libQt5XmlPatterns.la
/usr/lib64/libQt5XmlPatterns.prl
/usr/lib64/libQt5XmlPatterns.so.5.9.7
/usr/lib64/libqgsttools_p.prl
/usr/lib64/libqgsttools_p.so.1.0.0
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] why chown user:group wildcard in path /home/user/.*/* will modify all /home owner cociugcristina Linux - Server 11 05-07-2013 04:16 AM
Can I move /home partition under root partition arijit_2404 Linux - General 3 07-05-2007 12:01 AM
Sort installed packages by # of dependant packages installed brianez21 Debian 1 01-18-2006 05:06 PM
Partition Free Space - Move /home to the new partition gregkise Linux - General 5 12-16-2003 10:19 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:09 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration