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

Notices


Reply
  Search this Thread
Old 01-06-2017, 08:47 AM   #1
ag33k
Member
 
Registered: Mar 2013
Location: Portugal
Distribution: Slackware
Posts: 95

Rep: Reputation: Disabled
slackwarearm 14.2 - current avoid KDE packages on "slackpkg install-new"


I'm not used to use current.

But to update slackware I have to do

Code:
slackpkg update

slackpkg install-new

slackpkg upgrade-all
There is any way to avoid KDE packages? I didn't install KDE on my slackwarearm but I think that after
Code:
slackpkg install-new
KDE was installed.

There is any to avoid this?

Maybe using a blacklist or with a template?
 
Old 01-06-2017, 09:54 AM   #2
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 684

Rep: Reputation: 132Reputation: 132
install-new supposed to only install new packages after main release of system

so you might have gotten couple new kde packages

Code:
slackpkg blacklist kde
slackpkg blacklist kdei
should do it
 
1 members found this post helpful.
Old 01-06-2017, 10:16 AM   #3
ag33k
Member
 
Registered: Mar 2013
Location: Portugal
Distribution: Slackware
Posts: 95

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by glorsplitz View Post
install-new supposed to only install new packages after main release of system

so you might have gotten couple new kde packages

Code:
slackpkg blacklist kde
slackpkg blacklist kdei
should do it
I didn't select that packages during the installation!
It is normal that

Code:
slackpkg install-new
Install new packages that I didn't selected?
 
Old 01-06-2017, 11:21 AM   #4
Penthux
Member
 
Registered: Dec 2008
Location: Middlesbrough, UK
Distribution: Slackware
Posts: 242

Rep: Reputation: 71
Quote:
Originally Posted by ag33k View Post
I didn't select that packages during the installation!
It is normal that

Code:
slackpkg install-new
Install new packages that I didn't selected?
If you didn't de-select any packages which are available to install (i.e. removing the[*] on the left of the package name by highlighting the package and pressing spacebar) then slackpkg will install all packages which are selected in the list.
 
Old 01-07-2017, 03:04 PM   #5
ag33k
Member
 
Registered: Mar 2013
Location: Portugal
Distribution: Slackware
Posts: 95

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by glorsplitz View Post
install-new supposed to only install new packages after main release of system

so you might have gotten couple new kde packages

Code:
slackpkg blacklist kde
slackpkg blacklist kdei
should do it
Thanks!
That solved it!
 
Old 03-09-2019, 11:30 PM   #6
eduardr
LQ Newbie
 
Registered: Sep 2011
Posts: 28

Rep: Reputation: Disabled
Question Ran into this with slackwarearm-current

Sorry to revive this - I think there's some issue with slackpkg specific to slackwarearm that's still unresolved.

I recently installed slackwarearm-current on an RPi 3 B+ (thanks to Sarpi).

When I run slackpkg upgrade-all, it suggests all of the kde packages for installation, even though I never selected kde/kdei during the initial Slackware install.

I've never run across this with slackware x86/64. And blacklisting kde* was never necessary on x86/64.

I also had to blacklist sendmail (was suggesting that also) and the kernel packages.

Now I've got a very large blacklist and it also takes a very long time for the step "Looking for NEW packages to install. Please wait..." to run since it is looking at everything.

Last edited by eduardr; 03-09-2019 at 11:38 PM. Reason: More info
 
Old 03-10-2019, 11:22 AM   #7
eduardr
LQ Newbie
 
Registered: Sep 2011
Posts: 28

Rep: Reputation: Disabled
Lightbulb Figured it out, though the outcome isn't great

To answer my own question, it's because the slackwarearm-current Changelog.txt contains all those kde & sendmail packages as "Added.", whereas the slackware(64)-current Changelog.txt does not. This Alien Bob post provided the answer:

https://www.linuxquestions.org/quest...4/#post4907020

To illustrate, the output of these 2 commands is very different (many more packages marked as Added. in arm):

Code:
grep "Added\." slackwarearm-current/ChangeLog.txt
Code:
grep "Added\." slackware64-current/ChangeLog.txt
I don't know the reason why these Changelogs are so different but I'm sure there's some good reason having to do with how the slackwarearm project adopts packages from the x86 project.

I normally like to run "slackpkg install-new" on a regular basis along with the updates, since new packages do get added from time to time. It looks like I'll need to stop doing that on slackwarearm systems since the huge number of kde packages that show up swamp any other new packages that get added.

So on slackwarearm I'll be changing my standard alias:

Code:
alias spuu='slackpkg update; slackpkg upgrade-all; slackpkg install-new'
to

Code:
alias spuu='slackpkg update; slackpkg upgrade-all'
 
Old 03-10-2019, 01:34 PM   #8
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 790

Rep: Reputation: 596Reputation: 596Reputation: 596Reputation: 596Reputation: 596Reputation: 596
Quote:
Originally Posted by eduardr View Post
To answer my own question, it's because the slackwarearm-current Changelog.txt contains all those kde & sendmail packages as "Added.", whereas the slackware(64)-current Changelog.txt does not. This Alien Bob post provided the answer:

https://www.linuxquestions.org/quest...4/#post4907020

To illustrate, the output of these 2 commands is very different (many more packages marked as Added. in arm):

Code:
grep "Added\." slackwarearm-current/ChangeLog.txt
Code:
grep "Added\." slackware64-current/ChangeLog.txt
I don't know the reason why these Changelogs are so different but I'm sure there's some good reason having to do with how the slackwarearm project adopts packages from the x86 project.
Which lines specifically are different? Normally the change tags should be the same.

Also, there will be many more marked as "Added" because -current started off with no packages, so all were "Added" since in order to use -current, you had to reinstall from fresh because you cannot upgrade from 14.2.

Last edited by drmozes; 03-10-2019 at 03:08 PM.
 
  


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] [ENCHANCEMENT] slackpkg+: do not show the notices "pkglist is older than 24h..." and "remember to re-run 'slackpkg update''..."... yars Slackware 1 01-09-2016 09:56 AM
[SOLVED] Why "slackpkg install-new" tries to install kde packages? sejtn4u Slackware 4 03-24-2013 07:52 PM
".config" and ".kde" folders are being created under root directory (Slack Current) piratesmack Slackware 8 03-12-2011 11:06 PM
slackpkg/blacklist for AlienBob's current multilib and kde 4.4.2 packages damgar Slackware 7 04-08-2010 09:33 PM
Blacklisting packages with "slackpkg"??? Southpaw76 Slackware 2 05-19-2007 03:50 PM

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

All times are GMT -5. The time now is 11:52 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