Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
I think(!) I read somewhere it is a KDE-bug, you might want to search there on the KDE bug-tracker. This is a little bit contradicted by the openSuSE KDE 4.10.5 "release 1" moniker for the KDE-version I use mostly without trouble. But then KDE.org says they released 4.12.1 recently, perhaps you can simply upgrade...
when you install KDE from console (by using apt-get install or aptitude cron.*, it will upstream /dev/hdpi.
But when you install it with your distribution (eg. iLinux) it will install without creating /dev/hdpi.
Strange but dev know already.
And if you wait another day, you will find KDE 4.12.2 there instead of 4.12.1 and that version was compiled on Slackware 14.1 for maximum compatibility (will work perfectly on -current too, which is where I am typing this).
And if you wait another day, you will find KDE 4.12.2 there instead of 4.12.1 and that version was compiled on Slackware 14.1 for maximum compatibility (will work perfectly on -current too, which is where I am typing this).
Eric
Thanks, Eric. Last time I looked I thought 4.12.1 was only for -current. I'll grab 4.12.2 as soon as it's ready.
And if you wait another day, you will find KDE 4.12.2 there instead of 4.12.1 and that version was compiled on Slackware 14.1 for maximum compatibility (will work perfectly on -current too, which is where I am typing this).
Eric
Forgive me for asking this but I am relatively new to Linux: If I install the program from your repository am I then responsible to check periodically for new versions or will slackpkg take care of that every time that I run it? I think I know the answer but one never knows...
If you are new to Slackware and are willing to experiment, then you could read a bit about slackpkg+ which is an extension to slackpkg.
See http://alien.slackbook.org/blog/intr...-repositories/ which explains how slackpkg+ makes it a lot easier to maintain Slackware if you have 3rd party software installed from SLackware-compatible repositories (like my KDE repository).
Also if you installed multilib on top of your 64-bit Slackware, then slackpkg+ will make your life so much easier.
Slackware does not have an automatic update service, you are the admin and it leaves you full control, including the decision to perform upgrades... or not. You can schedule something like "slackpkg check-updates" as a regular cron job to get notified of updates per email.
If you are new to Slackware and are willing to experiment, then you could read a bit about slackpkg+ which is an extension to slackpkg.
See http://alien.slackbook.org/blog/intr...-repositories/ which explains how slackpkg+ makes it a lot easier to maintain Slackware if you have 3rd party software installed from SLackware-compatible repositories (like my KDE repository).
Also if you installed multilib on top of your 64-bit Slackware, then slackpkg+ will make your life so much easier.
Slackware does not have an automatic update service, you are the admin and it leaves you full control, including the decision to perform upgrades... or not. You can schedule something like "slackpkg check-updates" as a regular cron job to get notified of updates per email.
In my Slackware 14.1 (64-bit) I have already installed the multilib package that you offer, so slackpkg+ is definitely something that I am interested in. While I have not yet installed slackpkg+, I did read and re-read the instructions, including your "Introducing slackpkg+, an extensions to slackpkg for 3rd party repositories". I am a little bit confused as to how to set up /etc/slackpkg/slackpkgplus.conf.
Assuming that I have installed:
* The multilib for running 32-bit programs and KDE 4.12.1 packages, and
* Several packages from SlackBuilds.org
...I am not too sure what I need to enter in the PKGS_PRIORITY, REPOPLUS, and MIRRORPLUS sections of slackpkgplus.conf.
I think things should be this way:
PKGS_PRIORITY=(multilib:.* restricted:.* alienbob:.* ktown:.* slackbuilds:.*)
REPOPLUS=(slackpkgplus multilib ktown alienbob alienbob_current restricted)
MIRRORPLUS['multilib']=http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1
MIRRORPLUS['restricted']=http://taper.alienbase.nl/mirrors/people/alien/restricted_sbrepos/14.1/x86_64
MIRRORPLUS['alienbob']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/14.1/x86_64
MIRRORPLUS['ktown']=http://taper alienbase.nl/mirrors/alien-kde/14.1/latest/x86_64
MIRRORPLUS['slackbuilds']=http://http://slackbuilds.org/repository/14.1/
I think things should be this way:
PKGS_PRIORITY=(multilib:.* restricted:.* alienbob:.* ktown:.* slackbuilds:.*)
REPOPLUS=(slackpkgplus multilib ktown alienbob alienbob_current restricted)
MIRRORPLUS['multilib']=http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1
MIRRORPLUS['restricted']=http://taper.alienbase.nl/mirrors/people/alien/restricted_sbrepos/14.1/x86_64
MIRRORPLUS['alienbob']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/14.1/x86_64
MIRRORPLUS['ktown']=http://taper alienbase.nl/mirrors/alien-kde/14.1/latest/x86_64
MIRRORPLUS['slackbuilds']=http://http://slackbuilds.org/repository/14.1/
Did I get anything right??
SlackBuilds.org does not have a package repository, they just have build scripts. Therefore it can be removed from the slackpkgplus.conf - you will only get errors as long as you have it.
SlackBuilds.org does not have a package repository, they just have build scripts. Therefore it can be removed from the slackpkgplus.conf - you will only get errors as long as you have it.
Thanks for the help.
For multilib maintenance I also have to set
Code:
ALLOW32BIT=on
in /etc/slackpkg/slackpkgplus.conf, correct?
No, for multilib you do not have to set
Code:
ALLOW32BIT=on
. Multilib packages will be installed and maintained just fine without that flag.
The "ALLOW32BIT=on" will allow you to install 32-bit packages on a 64-bit Slackware computer using slackpkg. Note that this is a possibly unsafe operation because it can bring you into situations where you overwrite a 64-bit Slackware package (ARCH=x86_64) with a 32-bit Slackware package (ARCH=i486). The correct way of installing a 32-bit package in a multilib system us to use the "convertpkg-compat32" script on the package and create a "compat32" version of the 32-bit package which you can then install on your multilib computer. A "compat32" package is created in such a way that it will not overwrite important stuff from a 64-bit package.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.