@aikempshall
I you install the current Plasma5 build shipped by Eric, you do not need any KDE4 packages, also the KDevelop4 will conflict with the one shipped with Plasma5.
And in future, I recommend you to do a favor yourself: ignore the existence of
slackpkg and do your package management manually.
I for one, I keep local rsync repositories, then the Plasma5 I update manually, using the notes of Eric.
Even the Slackware itself I update via local rsync repositories and some small scripts.
Code:
#!/bin/sh
CWD=`pwd`
REMOTEREPO=rsync://bear.alienbase.nl/mirrors/alien-kde/
while true; do
rsync -avHz --delete --partial --progress $REMOTEREPO $CWD/alien-kde
sleep 10
done
This one syncs the Plasma5 repo (KTOWN).
Code:
#!/bin/sh
CWD=`pwd`
REMOTEREPO=rsync.osuosl.org::slackware/slackware-14.2/
while true; do
rsync -avz --delete --partial --progress $REMOTEREPO $CWD/slackware-14.2
sleep 10
done
This one syncs the stable 14.2, for the -current I use Eric's
mirror-slackware-current.sh
Code:
#!/bin/sh
CWD=`pwd`
SLACKREPO=$CWD/slackware64-current
if [ "$#" = "0" ]; then
echo "Usage: $(basename $0) headlines ..."; exit 1
fi
HEADNO="$1"
( cd $SLACKREPO/slackware64
cat ../ChangeLog.txt | head -n$HEADNO | grep ".t[gx]z" | cut -d: -f1 | \
grep -v "extra/" | \
grep -v "testing/" | \
grep -v "kde/" | \
grep -v "kdei/" | \
xargs upgradepkg --install-new
)
This one used as "slackupdate.sh <number of lines to process>" I use to update the -current, then the /etc/* files and the package removals I handle manually.
----------------------------------------------------------------------------------------------
I never felt the need to use
slackpkg in the last 20 years of Slackware usage.
And
IF I will adopt a package updater, probably it will be
slapt-get. Is so sad that our BDFL ignore its existence.
