LinuxQuestions.org
Visit Jeremy's Blog.
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 05-16-2018, 10:02 AM   #1
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 488

Rep: Reputation: 49
Installing ktown on top of current


These are some observations my journey to install ktown on top of current - following the instructions at

https://alien.slackbook.org/ktown/current/5/

I may have completely misunderstood the instructions!

Anyway as suggested in alienbob's README for installing ktown. I could save some effort by running
Code:
slackpkg remove kde
However, all that did for me was remove the following packages -

Quote:
kde-base-artwork-4.14.3-x86_64-2
kde-baseapps-4.14.3-x86_64-2
kde-dev-scripts-4.14.3-x86_64-2
kde-dev-utils-4.14.3-x86_64-2
kde-l10n-*-4.14.3-noarch-1
kde-runtime-4.14.3-x86_64-5
kde-wallpapers-4.14.3-noarch-1
kde-workspace-4.11.22-x86_64-4
kdeconnect-kde-0.8-x86_64-3
polkit-kde-agent-1-9d74ae3_20120104git-x86_64-2
polkit-kde-kcmodules-1-001bdf7_20120111git-x86_64-2
wicd-kde-0.3.0_bcf27d8-x86_64-2

From the above I've deduced that all "slackpkg remove kde" did for me was to remove those packages that contain the string kde in the package name that is not embedded in another string.

so it will remove kde-workspace and kdeconnect-kde but not kdevelop.

In alienbob's README it states that I could use the long method

Quote:
# removepkg /var/log/packages/*-4.14.3-*
# removepkg amarok
# removepkg kscreen
# removepkg kactivities
# removepkg kde-workspace
# removepkg kdeconnect-kde
# removepkg kdepim
# removepkg kdepimlibs
# removepkg kdev-python
# removepkg kdevelop-php
# removepkg kdevelop-php-docs
# removepkg libkscreen
# removepkg libmm-qt
# removepkg libnm-qt
# removepkg plasma-nm
# removepkg polkit-kde-agent-1
# removepkg polkit-kde-kcmodules-1
# removepkg wicd-kde

I duly did that, though some of them had already been removed by "slackpkg remove kde"

What I'm left with is

Quote:
kdelibs-4.14.38-x86_64-1
kdepim-runtime-4.14.10-x86_64-1
kdevelop-4.7.4-x86_64-1
kdevelop-pg-qt-1.0.0-x86_64-2
kdevplatform-1.7.4-x86_64-1
Should I remove these, or will slackpkg remove them when I do the upgrade?
 
Old 05-16-2018, 10:13 AM   #2
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Slackware 14.2 / Slackware 14.2 current / Void Linux / Peppermint Eight
Posts: 6,190

Rep: Reputation: 1192Reputation: 1192Reputation: 1192Reputation: 1192Reputation: 1192Reputation: 1192Reputation: 1192Reputation: 1192Reputation: 1192
I am not going to do all of them, but if you go to that page you posted the new stuff then manually click through each page using find to search for a match, I found the first one using only the name not with the version as that should be different so you'll never get a match.

kdelibs

https://alien.slackbook.org/ktown/cu...6_64/kde/kde4/

kdelibs-4.14.38-x86_64-1alien.txz

I would say it should be safe to remove them but a check for your own sanity to insure they are all there ready to replace the ones you have left. I'll leave that decision up to you.

if you're having a bit a an issue understanding from that in which I have written. That now you're going to have to change you line of thought on this matter. I'll be more than happy to say more as I've had complaints about my manner of explaining my reasoning in the typed word.

the line of thought should be.

The ones in question, they are part of the "kde package" therefor they have been dissociated because you removed the base KDE and they should be concidered orphaned.

So the plan of attack would be remove them after checking to insure they are all there in Aliens Package. then cross your fingers and install Aliens Package.

Wish you the best of luck.

Last edited by BW-userx; 05-16-2018 at 10:24 AM.
 
Old 05-16-2018, 10:23 AM   #3
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,266

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
@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.

Last edited by Darth Vader; 05-16-2018 at 02:07 PM.
 
2 members found this post helpful.
Old 05-16-2018, 11:25 AM   #4
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 488

Original Poster
Rep: Reputation: 49
Quote:
Originally Posted by Darth Vader View Post

And in future, I recommend you to do a favor yourself: ignore the existence of slackpkg and do your package management manually.
Must admit I started using slackware sometime before 2004 and also developed a number of scripts to keep me up to date with compat32, SBO and the Slackware most recent stable release. Never bothered with slackpkg until this week, thought it would make life easier!

When upgrading I always start with a completely new install and I will continue to do so. Hopefully, when the next release comes along it will have plasma (kde5) so it will be back to just keeping tabs on compat32, SBO and the Slackware and just dabble in current as and when.

I will take a look at what's in /slackware/slackware64-current/source/kde/src as my starting point as to what else needs to be deleted.
 
Old 05-16-2018, 11:34 AM   #5
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,266

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
KDE4 from Slackware use a meta-build, then it is more simple to just look in its packages set.
 
Old 05-16-2018, 02:55 PM   #6
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,029

Rep: Reputation: 4663Reputation: 4663Reputation: 4663Reputation: 4663Reputation: 4663Reputation: 4663Reputation: 4663Reputation: 4663Reputation: 4663Reputation: 4663Reputation: 4663
Quote:
Originally Posted by Darth Vader View Post
KDE4 from Slackware use a meta-build, then it is more simple to just look in its packages set.
Same for Plasma5.

Quote:
Originally Posted by aikempshall View Post
Code:
slackpkg remove kde
However, all that did for me was remove the following packages -
Strange. I wonder what you did to your slackpkg... when I run "slackpkg remove kde" on a default unaltered full install of Slackware (14.2, -current, does not matter) I get presented with a full list to remove, of all packages in the kde/ directory. Not just the few you mention with "kde" in the name.


Quote:
What I'm left with is
Code:
kdelibs-4.14.38-x86_64-1
kdepim-runtime-4.14.10-x86_64-1
kdevelop-4.7.4-x86_64-1
kdevelop-pg-qt-1.0.0-x86_64-2
kdevplatform-1.7.4-x86_64-1
Should I remove these, or will slackpkg remove them when I do the upgrade?
My README does not mention them as explicit removals because during one of the "upgradepkg --install-new" commands these packages will be upgraded to packages with the same name but coming from my Plasma5 repository.
 
2 members found this post helpful.
Old 05-17-2018, 02:36 AM   #7
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 686

Rep: Reputation: 215Reputation: 215Reputation: 215
When I used 'slackpkg remove kde' I had 194 packages selected. (Didn't count them, using 'slackpkg -dialog=off remove kde' gives you a total.
 
Old 05-17-2018, 03:29 AM   #8
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 488

Original Poster
Rep: Reputation: 49
Quote:
Originally Posted by chrisretusn View Post
When I used 'slackpkg remove kde' I had 194 packages selected. (Didn't count them, using 'slackpkg -dialog=off remove kde' gives you a total.
Thanks chrisretusn it's beginning to dawn on me what I've been doing wrong! In the case of converting to ktown the sequence I should have followed is

# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system
# slackpkg remove kde



whereas what I did was

# slackpkg update
# slackpkg remove kde

Having followed this incorrect procedure my physical system looked nothing like what slackpkg was expecting when I did the "slackpkg remove kde"


I've started again from the clean install of current from 16Feb2018. I'm 2 hours into the upgrade-all process. It's been a busy time on current over the last few weeks so I suspect I've still got some way to go.
 
Old 05-21-2018, 12:50 AM   #9
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 488

Original Poster
Rep: Reputation: 49
I've now tried

Code:
# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system
# slackpkg remove kde
Working a expected. Marking this as solved.

Thanks for all your help and encouragement.

Alex
 
1 members found this post helpful.
  


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] Today's -current icu4c upgrade broke ktown's sddm dugan Slackware 36 12-09-2017 04:50 AM
Preferred combination of stable/current and ktown? dugan Slackware 18 12-28-2016 03:20 AM
[SOLVED] Current and ktown 5 causing Gimp problems coralfang Slackware 21 09-16-2016 05:43 AM
[SOLVED] libreoffice not working on latest ktown on sw64-current; how to roll back to 4.10.5? michaelslack Slackware 3 12-05-2014 05:06 PM

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

All times are GMT -5. The time now is 10:53 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration